Nepomuk Strigi does not autostart with less than or equal to 1GB of RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase-runtime (Ubuntu) |
Fix Released
|
High
|
Jonathan Thomas | ||
Lucid |
Fix Released
|
High
|
Jonathan Thomas | ||
kubuntu-default-settings (Ubuntu) |
Fix Released
|
High
|
Jonathan Thomas | ||
Lucid |
Fix Released
|
High
|
Jonathan Thomas |
Bug Description
Binary package hint: kdebase-runtime
This is "branch" of the bug report: https:/
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://
Downloading the new kubuntu_
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/
3 rog131 30169 30141 0 20:09 ? 00:00:00 /usr/bin/
4 rog131 30170 30141 0 20:09 ? 00:00:00 /usr/bin/
5 rog131 30171 30141 0 20:09 ? 00:00:00 /usr/bin/
6 rog131 30172 30141 0 20:09 ? 00:00:00 /usr/bin/
7 rog131 30173 30141 0 20:09 ? 00:00:00 /usr/bin/
8 rog131 30174 30141 0 20:09 ? 00:00:00 /usr/bin/
9 rog131 30175 30141 0 20:09 ? 00:00:00 /usr/bin/
10 rog131 30176 30141 0 20:09 ? 00:00:00 /usr/bin/
11 rog131 30265 30141 3 20:13 ? 00:00:00 /usr/bin/
The nepomukserverrc has:
[Service-
First start=false
autostart=true
logout - login
Now the nepomukserverrc has:
[Service-
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/
3 rog131 30571 30540 0 20:17 ? 00:00:00 /usr/bin/
4 rog131 30572 30540 2 20:17 ? 00:00:00 /usr/bin/
5 rog131 30573 30540 0 20:17 ? 00:00:00 /usr/bin/
6 rog131 30574 30540 0 20:17 ? 00:00:00 /usr/bin/
7 rog131 30575 30540 0 20:17 ? 00:00:00 /usr/bin/
8 rog131 30576 30540 0 20:17 ? 00:00:00 /usr/bin/
9 rog131 30577 30540 1 20:17 ? 00:00:00 /usr/bin/
10 rog131 30578 30540 0 20:17 ? 00:00:00 /usr/bin/
The /var/crash is clean.
Changed in kdebase-runtime (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Jonathan Thomas (echidnaman) |
milestone: | none → ubuntu-10.04 |
Changed in kdebase-runtime (Ubuntu Lucid): | |
status: | New → Fix Committed |
Changed in kubuntu-default-settings (Ubuntu Lucid): | |
status: | New → Fix Committed |
assignee: | nobody → Jonathan Thomas (echidnaman) |
importance: | Undecided → High |
milestone: | none → ubuntu-10.04 |
tags: | added: kubuntu |
Changed in kubuntu-default-settings (Ubuntu Lucid): | |
status: | Fix Committed → Fix Released |
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 er.kcfg. It is imperative to set the first start key here, as default- settings led to the code preferring the k-d-s when-key- doesn't- exist value set in the code. I default- settings
nepomukserv
doing it in kubuntu-
setting over the default-
also included a few logic fixes, and this plus kubuntu-
10.04ubuntu23 should fix this bug. (LP: #564049)
-- Jonathan Thomas <email address hidden> Fri, 16 Apr 2010 10:43:54 -0400