Re: handling akonadi and nepomuk

On Wednesday, 2012-08-08, Martin (KDE) wrote:

> It seems to be a problem with session management. If I don't stop
> nepomuk by hand before logout I have 6 entries of nepomukservicestub and
> one nepomukcontroller in my ksmserverrc file. I don't know if the
> controller has to be handled by session management but the stubs should
> not be started by session manager. Is this a bug? Can this be configured
> somewhere?

I am not sure how Nepomuk controller is usually started, but I would have 
expected that to be either through autostart or D-Bus activation.

In any case I agree that its helper processes should only be controlled by the 
controller and not participate in session managment [1].

Not sure whether it is a bug or just hasn't been considered. You could try 
asking on the Nepomuk developer list.

Cheers,
Kevin

[1] Akonadi agents for example explicitly disable the session management 
capabilties they inherit from the KDE application infrastructure, they are 
managed by Akonadi's controller.

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQBQIiIhnKMhG6pzZJIRAvOyAJ48GclCQlevaHAdOkGkMtbAhS5YDQCdGH/t
+jRRep7Kq0lY3gLwYVKLSSc=
=TU6Q
-----END PGP SIGNATURE-----