Nepomuk Strigi does not autostart with less than or equal to 1GB of RAM

[Sam Rog]

Binary package hint: kdebase-runtime

This is "branch" of the bug report: https://bugs.launchpad.net/ubuntu/+source/kdebase-runtime/+bug/563021.

Jonathan Thomas wrote:
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.

Downloading the new kubuntu_89_strigi_ram_detection.diff. Compiling kdebase-runtime packages with it. Installing them.

Enabling Strigi Desktop File Indexer
The Strigi is up and running.

"ps -Af|grep nepo" is telling:

1 rog131 30141 1 0 20:09 ? 00:00:00 kdeinit4: nepomukserver [kdeinit]
2 rog131 30144 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukstorage
3 rog131 30169 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukremovablestorageservice
4 rog131 30170 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukpimoservice
5 rog131 30171 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukfilewatch
6 rog131 30172 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukontologyloader
7 rog131 30173 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukfileannotationservice
8 rog131 30174 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukusercontextservice
9 rog131 30175 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub digikamnepomukservice
10 rog131 30176 30141 0 20:09 ? 00:00:00 /usr/bin/nepomukservicestub nepomukqueryservice
11 rog131 30265 30141 3 20:13 ? 00:00:00 /usr/bin/nepomukservicestub nepomukstrigiservice

The nepomukserverrc has:

[Service-nepomukstrigiservice]
First start=false
autostart=true

logout - login

Now the nepomukserverrc has:

[Service-nepomukstrigiservice]
First start=false
autostart=true

but the Strigi is not running.

ps -Af|grep nepo:

1 rog131 30540 1 0 20:17 ? 00:00:00 kdeinit4: nepomukserver [kdeinit]
2 rog131 30547 30540 2 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukstorage
3 rog131 30571 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukpimoservice
4 rog131 30572 30540 2 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukontologyloader
5 rog131 30573 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukqueryservice
6 rog131 30574 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukremovablestorageservice
7 rog131 30575 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukusercontextservice
8 rog131 30576 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukfileannotationservice
9 rog131 30577 30540 1 20:17 ? 00:00:00 /usr/bin/nepomukservicestub digikamnepomukservice
10 rog131 30578 30540 0 20:17 ? 00:00:00 /usr/bin/nepomukservicestub nepomukfilewatch

The /var/crash is clean.

[Launchpad Janitor (janitor)]

This bug was fixed in the package kdebase-runtime - 4:4.4.2-0ubuntu4

---------------
kdebase-runtime (4:4.4.2-0ubuntu4) lucid; urgency=low

  * In kubuntu_89_ram_detection.diff, add a "First start=true" key to the
    nepomukserver.kcfg. It is imperative to set the first start key here, as
    doing it in kubuntu-default-settings led to the code preferring the k-d-s
    setting over the default-when-key-doesn't-exist value set in the code. I
    also included a few logic fixes, and this plus kubuntu-default-settings
    10.04ubuntu23 should fix this bug. (LP: #564049)
 -- Jonathan Thomas <email address hidden> Fri, 16 Apr 2010 10:43:54 -0400

[Sam Rog (samrog131)]

Fixed at here. Thank you.

[Cyberkilla (cyberkilla04uk-deactivatedaccount)]

It fixed it for me too, yet I have 2GB RAM.

My bug report (the one this forked from) is: https://bugs.launchpad.net/ubuntu/+source/kdebase-runtime/+bug/563021

Strigi is now running at startup.