Re: handling akonadi and nepomuk

Am 08.08.2012 10:26, schrieb Kevin Krammer:
> On Wednesday, 2012-08-08, Kevin Krammer wrote:
>> 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].
> 
> Maybe the problem is that the D-Bus command I suggested stops then wrong 
> service.
> Try to stop the Nepomuk controller instead of the server
> 
> qdbus org.kde.nepomukcontroller /MainApplication org.kde.KApplication.quit()

As the nepomukcontroller does not lead to any problem (neither delay nor
error message in the .xsession-error file) I am not sure if I should
stop it. Currently I don't know enough about nepomuk.

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