The bug is fixed for me, somehow..
The bug report mentioned in comment #10 is supposedly only affecting
people with =1GB RAM, but I have 2GB and the fix worked for me too.
Strigi is now running at startup.
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received
Cool. As long as it has a happy ending
** Changed in: kdebase-runtime (Ubuntu)
Status: Incomplete = Fix Released
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: kdebase-runtime (Ubuntu)
Status: New = Confirmed
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Rog131 on ubuntuforums.com suggest the problem might be linked to the
following patch :
kdebase-runtime (4:4.4.2-0ubuntu1) lucid; urgency=low
...
[ Jonathan Thomas ]
* Add kubuntu_89_strigi_ram_detection.diff. This will make Nepomuk disable
strigi on systems with less than or equal to 1GB of
I doubt that that is the cuase. When that patch disables strigi, it
writes autostart=false to the nepomukserverrc, but in Cyberkilla's case
we see that autostart is enabled. This points more towards one of the
many nepomukservicestub crashes.
but, to be certain, could you try replacing the
I doubt that that is the cuase. When that patch disables strigi, it
writes autostart=false to the nepomukserverrc, but in Cyberkilla's case
we see that autostart is enabled. This points more towards one of the
many nepomukservicestub crashes.
but, to be certain, could you try replacing the
Excuse me, it should look like this:
[Service-nepomukstrigiservice]
First start=false
autostart=true
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-runtime in
Just an FYI: I have 2GB RAM installed on this computer; the patch
/shouldn't/ affect me.
@Jonathan Thomas: Is there anything I can do to check whether
nepomukservicestub has crashed? The usual places seem to be devoid of
any evidence.
--
Nepomuk Strigi does not autostart
Description:Ubuntu lucid (development branch)
Release:10.04
Codename: lucid
Beta2
Linux alpha 2.6.32-21-generic
Qt: 4.6.2
KDE Development Platform: 4.4.2 (KDE 4.4.2)
kde4-config: 1.0
Memory 1G
What i have tried:
1)
With the gui. System Settings Advanced Desktop Search
@Cyberkilla
Hmm, you could ls /var/crash to see if apport picked anything up.
On an unrelated note, I suppose I should revert that patch. It's a shame that
strigi is such an unabashed memory hog though :/
Oh well, nothing to do about that for now.
--
Nepomuk Strigi does not autostart
So, since Cyberkilla has more than 1GB of RAM, it is a separate issue
from this patch.
@Sam
Could you file a new bug for the 1GB of RAM bug? I have an updated patch that
should fix things, it'd be great if you could test it and report your results
in the new bug: http://pastebin.com/RxynHfNR
New bug report added:
https://bugs.launchpad.net/ubuntu/+source/kdebase-runtime/+bug/564049.
(Nepomuk Strigi does not autostart with less than or equal to 1GB of RAM)
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a
@Jonathan Thomas: There are no crash reports in /var/crash for
anything except plymouthd and a few GIMP crashes.
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44149722/Dependencies.txt
--
Nepomuk Strigi does not autostart
https://bugs.launchpad.net/bugs/563021
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-runtime in
14 matches
Mail list logo
