Bug 194219 - nepomukserver started with Nepomuk turned off
Summary: nepomukserver started with Nepomuk turned off
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-26 22:09 UTC by Piotr Piotrowski
Modified: 2009-12-10 07:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Piotrowski 2009-05-26 22:09:59 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

File /usr/share/autostart/nepomukserver.desktop unconditionally starts
/usr/bin/nepomukserver that eats about 10 MB (RES in top) of my precious RAM, even if I turn off Nepomuk in settings. This is not the only app that wastes RAM in a similar fashion and if you add all the wasted RAM up it constitutes a significant amount.
Comment 1 Rex Dieter 2009-05-26 23:15:10 UTC
Confirmed.
Comment 2 Rex Dieter 2009-05-26 23:15:14 UTC
Confirmed.
Comment 3 Sebastian Trueg 2009-05-27 09:31:02 UTC
This is a design issue, not really a bug.
But the nepomukserver does not "waste" 10MB of memory. Not at all. The 10MB come from the shared libs that are loaded anyway: kdelibs, qt, and the like. nepomukserver itself does need close to no memory in idle mode.
However, I can see how it is disturbing to have the server running even though nepomuk is disabled. I am open to solutions (real solutions as in "patch", none of the kind "just stop it entirely when disabled.")
Comment 4 Kevin Kofler 2009-05-27 12:29:36 UTC
In https://bugzilla.redhat.com/show_bug.cgi?id=487322 the submitter suggested to use:
X-KDE-autostart-condition=nepomukserverrc:Basic Settings:Start Nepomuk:false
Comment 5 Sebastian Trueg 2009-05-27 12:48:03 UTC
very nice. I did not know about that. I will try to add that for KDE 4.4
Comment 6 Juha Tuomala 2009-06-29 17:07:13 UTC
Yeah, this hurts up here (estonia) too.
Comment 7 Rex Dieter 2009-06-29 17:49:47 UTC
Playing with this a bit, not sure if this is a bug in X-KDE-autostart-condition code or not, but adding:

X-KDE-autostart-condition=nepomukserverrc:Basic Settings:Start Nepomuk:true

doesn't seem to work, on a hunch I tried adding a bogus group/key without spaces in nepomukserverrc like:
[General]
Autostart=false

plus
X-KDE-autostart-condition=nepomukserverrc:General:Autostart:true

and this worked (ie, nepomukserver didn't start on login).

so I suspect that groups/keys with spaces may be a problem.
Comment 8 Rex Dieter 2009-06-29 17:59:02 UTC
ok, gremlins.

Seems nepomukserver was being stored as part of session management, and was getting restarted there.  after I purged that, things seem to work as advertised again (cross your fingers).
Comment 9 Piotr Piotrowski 2009-12-09 21:20:43 UTC
Can this bug be closed as fixed? I have kdebase-runtime-4.3.3-5.fc12.x86_64 installed and nepomuk is started conditionally as I expected.
Comment 10 Rex Dieter 2009-12-10 07:12:21 UTC
Yes, it has been committed to trunk/ awhile ago,

r989232 | lukas | 2009-06-29 14:10:48 -0500 (Mon, 29 Jun 2009) | 2 lines

forwardport (don't start nepomuk server unconditionally)