Summary: | =kde-base/kontact-4.4.* should depend on nepomuk | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aleister <maxtaager> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dschridde+gentoobugs, esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 313999 |
Description
Aleister
2010-02-12 08:50:54 UTC
(In reply to comment #0) > QMutex::unlock: mutex lock failure: > > Expected Results: > kontact should work :-) The mutex local failure was fixed with soprano-2.4.0.1... (In reply to comment #1) > (In reply to comment #0) > > QMutex::unlock: mutex lock failure: > > > > Expected Results: > > kontact should work :-) > > The mutex local failure was fixed with soprano-2.4.0.1... > i dont think that was the problem because how could kontact get a lock on something that dosent exists Connecting to local socket "/home/max/.kde4/share/apps/nepomuk/socket" because of lacking nepomuk? as i understand it kdepim needs nepomuk (so it can put stuff in the virtuoso database)if this is optional it could be fixed with a useflag etc. But before we go down this road. Somebody should figure out if nepomuk is really needed or is optional for kde-pim (or some parts of it). I think it should be $(add_kdebase_dep kdepim-runtime) in RDEPEND, same as kmail reavertm, can you check? Fixed, thanks for reporting and to all involved! Yes, kdepim-runtime is the way to go. |