Version: 4.1 (using KDE 4.7.0) OS: Linux Since Nepomuk was introduced, I was never able to make it work or even let it live. After installing a new version of KDE, I always delete all the binaries in (rm /usr/bin/nepom* /usr/bin/akonadi*) and chmod 0 /usr/sbin/mysqld because it causes all kind of problems and grief: System loads over 20, 100% CPU usage, crashing my KDE session or locking up the system. Not to mention that it hogs my hard disk or memory even when it behaves. I have seen this on several different computers, different versions of KDE and the kernel. When ever I look into my process list, I only find more processes which get in each others way to hog some resource (CPU or disk). It really sucks. Worse, there is no way to stop this from happening because to disable Nepomuk, I need to start systemsettings - which is already too late. From my point of view, the software is clearly not ready for production or general use. Now you will probably feel that this request is asking for too much. Can at least please disable this **** by default? Or install a kill switch that stops it when it uses too many resources? Reproducible: Always Steps to Reproduce: Install KDE, log in. Expected Results: Make sure that Nepomuk and related tool never use more than 5% of the CPU, 5% of RAM, 5% of the IO bandwidth and 5% of the hard disk. If anything needs more, ask the user but never hog the system. If you can't do this, disable the services by default so people can at least log in. My Nepomuk binaries come from kdebase4-runtime-4.7.0-8.1.x86_64 I installed them from http://download.opensuse.org/repositories/KDE:/Release:/47/openSUSE_11.4/
Hi, You do know that you can simply disable nepomuk right? It's in System Settings -> Desktop Search. Just disable it there and you're done. No need to remove the binaries. As for removing it or disabling by default... That's probably not gonna happen.
As I said, this isn't possible: The load on the machine is so high that I can't even open the menu to start "system settings". What happens here is: I get the greeter, I log in, I get the desktop. Load grows and grows (I know because I logged in from remote as root via ssh) until it hits about 26. Then KDE crashes and I'm back at the log-in screen.
This is obviously a wontfix for me. :)
Yes, it's pretty obvious that software quality is a nice to have for many people involved with Nepomuk and related tools. I updated last week to openSUSE 12.2 which contains tracker-miner-firefox which somehow connects Firefox to Nepomuk with the result that Firefox now crashes all the time. Thanks for wasting several hours of my time and support people from Firefox and Novell. We really appreciate your efforts. I suggest to write a plugin for PAM to search for users names in passwd.txt; that way, you could even prevent anyone from using their computer.
(In reply to comment #4) > Yes, it's pretty obvious that software quality is a nice to have for many > people involved with Nepomuk and related tools. I updated last week to > openSUSE 12.2 which contains tracker-miner-firefox which somehow connects > Firefox to Nepomuk with the result that Firefox now crashes all the time. Please contact opensuse about this. The tracker-minor-firefox is related to "TRACKER", and has nothing to do with Nepomuk. So, please direct your frustration towards the tracker developers. > > Thanks for wasting several hours of my time and support people from Firefox > and Novell. We really appreciate your efforts. > You're welcome. Btw, you can just go to System Setting -> Desktop Search -> Disable Nepomuk, and then we do not bother you any more. Though, in this case we weren't bothering you in the first place. > I suggest to write a plugin for PAM to search for users names in passwd.txt; > that way, you could even prevent anyone from using their computer. Duly noted. Maybe we can even post the file's content on the kde website?
Thank you for your quick response. As I said before, there is no way to disable Nepomuk. I'm not sure where you get the idea that the option does what it says. But since you will doubt me, here is my process list: adigulla 22620 22497 0 Sep06 ? 00:00:00 kdeinit4: nepomukserver [kdeinit] adigulla 22623 22620 0 Sep06 ? 00:00:09 /usr/bin/nepomukservicestub nepomukstorage adigulla 22673 1 0 Sep06 ? 00:00:00 /usr/bin/nepomukcontroller -session XXXX adigulla 23594 22646 0 Sep06 ? 00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder adigulla 23873 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub digikamnepomukservice adigulla 23877 22620 0 Sep06 ? 00:00:07 /usr/bin/nepomukservicestub nepomukfilewatch adigulla 23878 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub nepomukqueryservice adigulla 23879 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub nepomukbackupsync Together, these processes occupy 5GB virtual address space. Maybe we have a different definition of "disabled". For me, it means to turn something off. Maybe it means "handicapped" for you. That view wouldn't be shared by many people, though. At least they don't seem to take much CPU right now - just 15s. But as I said in this bug report before (does anyone ever read them?), this might be pure chance. As for the relation between TRACKER and Nepomuk: Tracker uses W3C standards for RDF ontologies using *Nepomuk* with SPARQL to query and update the data.
(In reply to comment #6) > Thank you for your quick response. > > As I said before, there is no way to disable Nepomuk. I'm not sure where you > get the idea that the option does what it says. But since you will doubt me, > here is my process list: > > adigulla 22620 22497 0 Sep06 ? 00:00:00 kdeinit4: nepomukserver > [kdeinit] > adigulla 22623 22620 0 Sep06 ? 00:00:09 /usr/bin/nepomukservicestub > nepomukstorage > adigulla 22673 1 0 Sep06 ? 00:00:00 /usr/bin/nepomukcontroller > -session XXXX > adigulla 23594 22646 0 Sep06 ? 00:00:00 > /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder > adigulla 23873 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub > digikamnepomukservice > adigulla 23877 22620 0 Sep06 ? 00:00:07 /usr/bin/nepomukservicestub > nepomukfilewatch > adigulla 23878 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub > nepomukqueryservice > adigulla 23879 22620 0 Sep06 ? 00:00:00 /usr/bin/nepomukservicestub > nepomukbackupsync > > Together, these processes occupy 5GB virtual address space. Maybe we have a > different definition of "disabled". For me, it means to turn something off. > Maybe it means "handicapped" for you. That view wouldn't be shared by many > people, though. > > At least they don't seem to take much CPU right now - just 15s. But as I > said in this bug report before (does anyone ever read them?), this might be > pure chance. > > As for the relation between TRACKER and Nepomuk: Tracker uses W3C standards > for RDF ontologies using *Nepomuk* with SPARQL to query and update the data. That's a different issue then the one you initially opened. Initially you just asked for everything to be disabled by default. If you disabled nepomuk and you're still seeing those nepomuk services then i'd suggest you to open a new bug report telling that. I personally don't know if that's a bug or a feature.. I can't reproduce it at this moment since my archlinux went broken..