Bug 147833

Summary:	kded uses 100% cpu and hangs pc
Product:	[I don't know] kde	Reporter:	Gehold Bertin <NewsAssi>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED REMIND
Severity:	crash	CC:	l.lunak, pavel_mendl
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gehold Bertin 2007-07-13 07:59:46 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages

Hi!

Using Ubuntu 6.10 and 7.04 kdeinit hangs on login.

Problems:
* kdeinit needs 1 CPU with 100%
* No automounting (kio?)
* No wallet and no program using wallet can run
* Konqueror start, but try to enter a link, hangs the whole pc (no switching to console CTRL-ALT-F1 is possible)
* Only a few only (???) no kde programs like Firefox works

Killing kdeinit make whole system instable...

ps aux:
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
...
user      6020 84.0  0.5  36412 17784 ?        R    22:40   9:11 kded [kdeinit] --new-startup                               

My solution:
Deactivating KDE Session restoring (Ubuntu: System Settings -> Advancend -> Session Manager -> On Login: Start with an empty session)

Seem some common problem:
http://lists.kde.org/?l=kde-devel&m=104994205910346&w=2
http://lists.kde.org/?l=kde-core-devel&m=107214404421414&w=2
http://www.linuxforums.org/forum/linux-programming-scripting/49666-kdeinit-uses-50-cpu.html
http://www.linuxquestions.org/questions/showthread.php?t=330884 
http://forum.ubuntuusers.de/topic/98713/

Comment 1 Lubos Lunak 2008-05-30 11:34:25 UTC

As the output suggests, it's kded, not kdeinit. Also, the posted links seem to be only a random collection of '<something> uses cpu' and at least half of those are unrelated.

Please attach gdb to kded as described in http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB and provide the backtrace to identify which module of kded is responsible.

Comment 2 Lubos Lunak 2008-06-30 11:39:18 UTC

Waiting for response, no useful information.

Comment 3 Pavel Mendl 2008-12-29 18:16:24 UTC

Confirming this bug on KDE 3.5.9 / GNU/Linux (Debian Lenny). Just today I mentioned this behaviour, when playing with KSysGuard and finding 100% usage on one CPU.
Seems some recent kwallet/kmail failures are related: if you place "kded 100%" into Google, you will get plenty of (quite relevant, yet unresolved) bugreport links at least for Ubuntu.
Killing kded from KsysGuard tasklist works for me (maybe I am just lucky having two CPUs), but seems I (without noticing) let kmail to store password somewhere out of kwallet... Anyways this is either unsecure either annoying.

I can not comply the gdb tutorial, as this situation appears during initial startup (via Kde login), so I have no way how to "prepend" gdb into some "command line" as this is transparent to me during boot/login phase...
However I am ready to colaborate on testing, if you supply some practicable instructions.