Version: 4.6 (using KDE 4.6.2) OS: Linux After resuming from suspend or hibernate the desktop freezes, although keyboard seems to continue working. Moving the mouse doesn't move the cursor. I am able to switch to another terminal by using Ctrl+Alt+F2 and see that Kded4 is with 100% cpu usage. Looking at the dmesg output after resume, the only possibly relevant errors I see are these lines: [ 5159.368342] render error detected, EIR: 0x00000010 [ 5159.368342] page table error [ 5159.368342] PGTBL_ER: 0x00000003 [ 5159.368342] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking [ 5159.368342] render error detected, EIR: 0x00000010 [ 5159.368342] page table error [ 5159.368342] PGTBL_ER: 0x00000003 Reproducible: Always Steps to Reproduce: 1. Suspend computer 2. Resume 3. Try to do anything Actual Results: Can't do anything as kwin is frozen. Expected Results: KWin isn't frozen and I'm able to use my computer. This is an Atom N270 system with i945G and all packages up to date.
I forgot to add that killing kded un-freezes the system.
If this is reproducible, please disable kded4 modules in "System Settings > Startup and Shutdown > Service Manager" to see which one is the culprit. Some modules cannot be disabled there. To disable such a module, remove its .desktop file from /usr/share/kde4/services/kded/, run kbuildsycoca4, and restart kded4. The information which module causes the problem helps fixing the issue.
Created attachment 59814 [details] the setup I have the same problem, running Awesome on ArchLinux with some KDE 4.6.3 apps. This is how "systemsettings -> Startup and Shutdown > Service Manager". Network status is running although I don't know why.
I ran the test in comment #2 (removing .desktop file, and restarting kded4) and found that these two files are causing problems: networkstatus.desktop and networkmanagement.desktop After removing them, I no longuer have the 100% cpu problem when doing suspend/resume. I'm not sure what they are useful for as my network is still working (CDMA cellular card)
Ricardo, can you confirm that the networkstatus module causes the issue?
Sorry, I can't confirm if it works since I'm no longer using KDE. If the user in comment #4 managed to fix it by removing those files and nobody else complained about this, maybe it's safe to say that those are the only files causing problems.
*** This bug has been marked as a duplicate of bug 272527 ***
On Kubuntu natty, updated to kde 4.6.3, I confirm that kded4 goes to 100% cpu usage (and becomes unresponsive) whenever a ppp connection via 3G mobile is started or stopped. I also confirm that going to "System settings"->"Startup and Shutdown"->"Service Manager" and stopping+disabling "Network status" seems to solve the issue. I believe that here we have 2 problems. The first one is obviously network status that evidently manages locking up in active wait of something. The second and IMHO much more serious one is the model by which services are managed by kded4 where one single service can lock up the whole kded4. Indeed note that when the issue reported in this bug report happens, not only kded4 starts eating up 100% cpu, it also becomes unresponsive. This is evidently declared by the "System settings"->"Startup and Shutdown"->"Service Manager" that gets grayed out, with a popup saying that kded4 cannot be contacted. To someone that is not an expert in kded4 internals like me, this is quite reminiscent of older OSes using cooperative multitasking models, where one misbehaving "task" could bring the whole system down. Please at least add a watchdog or something in its lines, so that when a kded4 service locks it can be identified, reported to the user and disabled.