Bug 258157

Summary:	akonadi self-test doesn't find nepomuk dbus search service at startup
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Fabio Rossi <rossi.f>
Component:	libakonadi	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dvratil, gstengel, joker777vs.666, me
Priority:	NOR
Version:	4.5
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:	http://commits.kde.org/kdepimlibs/4b3e3fa8692f2701e146db2ea8c364ae8d7372a9	Version Fixed In:	4.13
Sentry Crash Report:
Attachments:	akonadi-selftest-report-20101128-at-startup.txt akonadi-selftest-report-20101128-after-startup.txt

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.