[opensuse] nepomukfromhell - 99% of CPU
List, I had removed /usr/share/autostart/nempmuk..desktop for the specific reason of preventing that Beagle like application from starting. After a couple of hours, my machine is brought to its knees. I knew what the problem was before I even ran killall $(ps ax | grep nepomuk), and sure enough the beast was back. I rechecked /usr/share/autostart/ and there was no nepomuk. How in the heck did it start on its own after I had removed the autostart entry and after I had rebooted without it present?? To see how nepomuk cripples a systems, see: http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/nepomuk-s... http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/nepomuk-s... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jul 26, 2009 at 5:04 PM, David C. Rankin<drankinatty@suddenlinkmail.com> wrote:
I had removed /usr/share/autostart/nempmuk..desktop for the specific reason of preventing that Beagle like application from starting. After a couple of hours, my machine is brought to its knees. I knew what the problem was before I even ran killall $(ps ax | grep nepomuk), and sure enough the beast was back. I rechecked /usr/share/autostart/ and there was no nepomuk. How in the heck did it start on its own after I had removed the autostart entry and after I had rebooted without it present??
Nice. What type of system are you running? Evidently, nepomuk is integrated in KDE4, so I don't think it will be removable......whatever happened to creating modular components that could be added and removed easily? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 23:48:52 Larry Stotler wrote:
Evidently, nepomuk is integrated in KDE4, so I don't think it will be removable......whatever happened to creating modular components that could be added and removed easily?
It's enabled by kdeinit, exactly like every other kde service there ever was for kde3 or kde4. Easily enabled or disabled in the KDE control center. But I still think it would be worth letting it run to completion, and then actually have a look at it to see if it might be useful. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 04:48:52 pm Larry Stotler wrote:
Nice. What type of system are you running?
This is my old Toshiba P35 laptop with 11.0 and kde4 installed along side kde3. Good combination. kde4 is runable, looks good, but you have to kill and restart a lot of apps due to ... well kde4. I was really encouraged when I first loaded 4.3 beta 2 a couple of months ago. Now after have spent months with it (currently with 4.2.98) my enthusiasm meter has dropped significantly. I spend more time fighting what doesn't work than working. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 23:04:19 David C. Rankin wrote:
List,
I had removed /usr/share/autostart/nempmuk..desktop for the specific reason of preventing that Beagle like application from starting. After a couple of hours, my machine is brought to its knees. I knew what the problem was before I even ran killall $(ps ax | grep nepomuk)
That command line makes no sense at all. killall expects the name of a program as parameter, not the compound output you get from "ps ax"
, and sure enough the beast was back. I rechecked /usr/share/autostart/ and there was no nepomuk.
How in the heck did it start on its own after I had removed the autostart entry and after I had rebooted without it present??
Go to "configure desktop" in the menu, then click on "advanced", and then on "desktop search" and deselect "Enable Nepomuk Semantic Desktop". But how about letting it run to completion just once. It just needs to run through everything once, after that it just looks at changes, so the intensive scan won't be there. After that, you might even find it useful Incidentally, if a hard drive scan brings your machine to its knees, you need to look at your hardware. It scanned my entire machine, and I didn't even notice it was there Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 23:04:19 David C. Rankin wrote:
and sure enough the beast was back.
Actually, forget what I said. It just occurred to me that nepomuk doesn't scan anything. That's strigi (which btw is disabled by default). nepomuk just lets you tag files manually, so you can search for the tags later. If it consumes 100% CPU, it's a bug and you need to report it Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 05:08:02 pm Anders Johansson wrote:
On Sunday 26 July 2009 23:04:19 David C. Rankin wrote:
and sure enough the beast was back.
Actually, forget what I said. It just occurred to me that nepomuk doesn't scan anything. That's strigi (which btw is disabled by default). nepomuk just lets you tag files manually, so you can search for the tags later. If it consumes 100% CPU, it's a bug and you need to report it
Anders
Anders, I agree with your earlier posts that if I don't notice it, I don't care if it runs. But when something takes 99% of the CPU and the laptop fans start sounding like it is preparing for take-off. Something has to go. Whatever is running, it is running under "nepomukservices" and it's going wild. Eliminating nepomuk from autostart seems to minimize the run-away occurrences. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 27 July 2009 02:09:42 David C. Rankin wrote:
I agree with your earlier posts that if I don't notice it, I don't care if it runs. But when something takes 99% of the CPU and the laptop fans start sounding like it is preparing for take-off. Something has to go. Whatever is running, it is running under "nepomukservices" and it's going wild.
Eliminating nepomuk from autostart seems to minimize the run-away occurrences.
Understood. It's a known issue, but as far as I know, only if strigi is enabled (in the kde control center -> advanced -> desktop search, as I mentioned), and the "wrong" storage backend is used. Without strigi I have never seen it, so if you have strigi enabled and still see the CPU load, you should report it Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 27 July 2009 02:24:44 Anders Johansson wrote:
never seen it, so if you have strigi enabled and still see the CPU load, you should report it
Sorry, I (obviously) meant: if you *don't* have strigi enabled.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 July 2009 05:08:02 pm Anders Johansson wrote:
On Sunday 26 July 2009 23:04:19 David C. Rankin wrote:
and sure enough the beast was back.
Actually, forget what I said. It just occurred to me that nepomuk doesn't scan anything. That's strigi (which btw is disabled by default). nepomuk just lets you tag files manually, so you can search for the tags later. If it consumes 100% CPU, it's a bug and you need to report it
Anders
On the 4.3-0.1 release nepomuk went to 103% and just stuck there. That was *without* strigi indexer even being selected. I had to remove the autostart and kill nepomuservices to get my cpu back. As a test, I then set strigi to start and reenabled nepomuk autostart. Nepomuk behaved ok, small cpu load and then finished. Nothing like it was doing when strigi was not checked. Go figure... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Anders Johansson -
David C. Rankin -
Larry Stotler