Summary: | nepomukserver started with Nepomuk turned off | ||
---|---|---|---|
Product: | nepomuk | Reporter: | Piotr Piotrowski <ppp5> |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kevin.kofler, rdieter, trueg, tuju |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Piotr Piotrowski
2009-05-26 22:09:59 UTC
Confirmed. Confirmed. 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.") 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 very nice. I did not know about that. I will try to add that for KDE 4.4 Yeah, this hurts up here (estonia) too. 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. 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). 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. 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) |