> On 01/12/2011 12:25 PM, John A. Sullivan III wrote:
>> Hello, all.  One of the bug reasons we avoid KDE4 is the resource drain
>> of running Nepomuk.  However, we are finding it is always starting on
>> our Trinity desktops.  How does one prevent Nepomuk from starting?
>> Thanks - John
>>
>>
>
>
> This is from
> http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/NepomukServer
>
> The Nepomuk Server is a daemon which hosts all Nepomuk service including
> the main Nepomuk data repository. In normal operation it is started
> through KDE's autostart feature when logging into KDE. Starting it
> manually is as simple as typing "nepomukserver". This will start the
> daemon and all services.
>
>
> HTH, Jim
>

It's actually the XDG autostart that handles it from what I can tell,
otherwise Trinity would not be able to start it.

Of course, XDG autostart is part of the KDE autostart sequence, so the
techbase article is correct for most users.  Just wanted to point out the
difference in the context of a non-KDE window system.

Tim