Is this whole strigi/nepomuk taking too much resources thing, something that is going to get fixed?

After upgrading to 10.4, I switched my Ubuntu back to KDE 3.5 (using KDE 3.5.11 Trinity) due to all sorts of instabilities happening to KDE 4.4 that weren't in KDE 4.3. I'm suspecting now that this nepomuk/strigi thing was the cause of ALL instabilities I had with KDE 4.4 (including having to reboot twice due to the same compositing message mentioned in this thread).

Nepomuk has:

-left my CPU running at 100% for a whole night without me knowing
-made KDE 4.4 hang/crash on multiple occasions
-created 12 or more processes of the same name that were hard to kill, came back, and so on
-slowed down usage of any application due to taking resources all the time
-this on a quad core PC with 3GB RAM

So, is it going to get fixed?

Ideally, nepomuk (and other related services such as strigi and virtuoso-t) would take no resources unless you actively use it (and not 100% and 12 processes in that case!).

Each of the "nepomukservicestub" processes does a different job as far as I am aware, and are respawned up to 5 times by Nepomuk Server if they become unavailable ( such as if they crash or are killed )

Just interested, which process was occupying 100% CPU usage, and did you have Strigi indexing enabled?

bcooksley wrote:Just interested, which process was occupying 100% CPU usage, and did you have Strigi indexing enabled?

To be honest, I don't remember anymore.

Here's what I remember:

First I had Ubuntu 9.4, with Gnome. In Oktober 2009 I upgraded to Ubuntu 9.10 with Gnome. Later in Ubuntu 9.10 I switched to Kubuntu, which gave me KDE 4.3.

I never had problems with Kubuntu 9.10. So, whether or not nepomuk was already installed on a stock Kubuntu 9.10 ( I don't know myself ), it didn'g give those problems there.

Then when Ubuntu 10.4 was released, I upgraded to Kubuntu 10.4, with KDE 4.4, and then the problems began.

The day after the upgrade everything was very slow, I did "top", and discovered all the nepomuk binaries running at 100% CPU (this was my first introduction to nepomuk BTW).

I searched the Ubuntu forums and read something about disabling semantic desktop search in the KDE 4 settings, so I did that, and I think that it's likely that I disabled all checkboxes there (so probably strigi too, but that checkbox gets grayed out when disabling the topmost checkbox so who knows).

But anyway, the system still showed problems after that. I think both nepomuk executables and virtuoso-t things were still running and slowing down my system after that.

One or two weeks of KDE 4 bugs related to icons in taskbar moving around, twice the message about disabled compositing mentioned in this thread, and also twice or so KDE *hanging*, I gave up on KDE 4 once again and went for KDE 3.5.

After installing KDE 3.5, the nepomuk processes were STILL alive and active, and STILL slowing down my system, even when disabled in the KDE4 control panel.

So then I used synaptic to uninstall everything that had "nepomuk" or "virtuoso" in its name (iirc I had to delete some files manually too, I think I eventually did a recursive find (the good old find) for files with nepomuk in their name), and now I can productively use this computer again.

That is certainly not expected behaviour, as Nepomuk should shut down once disabled in System Settings. Were you using any KDE 4 PIM applications?

bcooksley wrote:That is certainly not expected behaviour, as Nepomuk should shut down once disabled in System Settings. Were you using any KDE 4 PIM applications?

Not that I know of, unless an application running in the background enabled by default by Kubuntu does it, or maybe Thunderbird or another application uses it somehow...

As far as I am aware Thunderbird doesn't use Nepomuk.

Can you reproduce under a new user? ( ie. reinstall the KDE packages, then create a new user and log in )

Not at the moment sorry (this is a work PC). If I ever try KDE 4 again in a next Ubuntu release and I encounter the problem again, I'll try to study it in more detail before killing it off and try to post the better info.