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
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
One way is to completely remove the KDE4 packages responsible--under Ubuntu they are:
libnepomuk4 kdebase-runtime kdebase-runtime-data
Otherwise, you would have to hunt down Nepomuk's XDG startup file (it isn't called nepomuk for some inscrutable reason) and remove it.
Tim
On Wed January 12 2011 11:25:23 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
Hi John,
There should be no need for Nepomuk to be installed unless you also have (some or all of) KDE 4 installed alongside Trinity.
Which version of which distro are your working in? In Debian, for example, you can ask "aptitude why kdebase-runtime".
Note that Nepomuk can be disabled if you see it running by clicking on the icon in the systray and then basic settings.
--Mike Bird
On Wed, 2011-01-12 at 12:06 -0800, Mike Bird wrote:
On Wed January 12 2011 11:25:23 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
Hi John,
There should be no need for Nepomuk to be installed unless you also have (some or all of) KDE 4 installed alongside Trinity.
Which version of which distro are your working in? In Debian, for example, you can ask "aptitude why kdebase-runtime".
Note that Nepomuk can be disabled if you see it running by clicking on the icon in the systray and then basic settings.
--Mike Bird
Thanks, all. I'm guessing this is the result of migrating the Squeeze system from KDE4 as I do not see the systray icon to disable it. I do not see it in the various administration tools yet it is running. I'll see about pulling out the packages - John
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
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
On 2011/01/12 14:25 (GMT-0500) John A. Sullivan III composed:
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?
A system level way that ought to both prevent it from starting, and survive updates/upgrades:
# mv /usr/bin/nepomukserver /usr/bin/nepomukserver-orig # touch /usr/bin/nepomukserver # chattr +i /usr/bin/nepomukserver
Hi Felix,
# mv /usr/bin/nepomukserver /usr/bin/nepomukserver-orig # touch /usr/bin/nepomukserver # chattr +i /usr/bin/nepomukserver
this seems to do the job. Thanks.
On Fri, 2011-01-14 at 09:11 +0100, HHa wrote:
Hi Felix,
# mv /usr/bin/nepomukserver /usr/bin/nepomukserver-orig # touch /usr/bin/nepomukserver # chattr +i /usr/bin/nepomukserver
this seems to do the job. Thanks.
I took the suggested package uninstall route and it removed a pile of packages. The system seems much lighter and quicker now but I don't need KDE4 at all. Thanks to all - John
-
Felix Miata -
HHa -
Jim Barnes -
John A. Sullivan III -
Mike Bird -
Timothy Pearson