Bug 258157 - akonadi self-test doesn't find nepomuk dbus search service at startup
Summary: akonadi self-test doesn't find nepomuk dbus search service at startup
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: libakonadi (show other bugs)
Version: 4.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 299725 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-11-28 11:30 UTC by Fabio Rossi
Modified: 2014-03-14 16:28 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.13


Attachments
akonadi-selftest-report-20101128-at-startup.txt (4.58 KB, text/plain)
2010-11-28 11:31 UTC, Fabio Rossi
Details
akonadi-selftest-report-20101128-after-startup.txt (4.68 KB, text/plain)
2010-11-28 11:31 UTC, Fabio Rossi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Rossi 2010-11-28 11:30:31 UTC
Version:           4.5 (using KDE 4.5.3) 
OS:                Linux

I have the Nepomuk semantic desktop enabled without strigi file indexer. Akonadi is also enabled with a SQlite backend.

At startup the akonadi self-test finds an error related to a not running nepomuk dbus search service (attached akonadi-selftest-report-20101128-at-startup.txt) but if I re-run the self-test again the error is gone (attached akonadi-selftest-report-20101128-after-startup.txt).

$ qdbus org.kde.NepomukServer /servicemanager availableServices
nepomukontologyloader
nepomukmigration1
nepomukqueryservice
digikamnepomukservice
nepomukstorage
nepomukactivitiesservice
nepomukremovablestorageservice
nepomukstrigiservice
nepomukfilewatch

$ qdbus org.kde.NepomukServer /servicemanager isServiceRunning nepomukqueryservice
true

This means there is a race condition at startup, isn't it?

Reproducible: Always
Comment 1 Fabio Rossi 2010-11-28 11:31:35 UTC
Created attachment 53820 [details]
akonadi-selftest-report-20101128-at-startup.txt
Comment 2 Fabio Rossi 2010-11-28 11:31:53 UTC
Created attachment 53821 [details]
akonadi-selftest-report-20101128-after-startup.txt
Comment 3 Gerhard 2011-02-13 20:46:20 UTC
Since I've upgraded to KDE 4.6.0, I've exactly the same problem, nepomuk is not recognized running at login, but if I perform another akonadi self test after login, everything is reported OK, nepomuk is actually running.

What is important in this context is that I only get the problem if I activate the display of e-mails or RSS feeds in the system tray, i.e. kontact is started at KDE login. Otherwise no problems...

Furthermore, only the first time somebody logs in (with kontact being started) after a cold boot gets the error message. If you log off an on again, there's no problem, too.
Comment 4 Vishesh Handa 2012-05-22 13:48:01 UTC
*** Bug 299725 has been marked as a duplicate of this bug. ***
Comment 5 Vishesh Handa 2012-05-22 13:53:05 UTC
This is UPSTREAM issue. 

We need some way to specify that Nepomuk should be started before Akonadi. One option is systemd and the other is to port Ivan's solution to KDE SC.

http://ivan.fomentgroup.org/blog/2011/11/02/start-active/
Comment 6 Daniel Vrátil 2014-03-14 16:28:07 UTC
We don't check for Nepomuk anymore in KDE 4.13.