Bug 92501

Summary: 100% CPU usage at startup, blocks konqueror
Product: [Frameworks and Libraries] kdelibs Reporter: Greg Martyn <greg.martyn>
Component: kdedAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Greg Martyn 2004-11-01 01:28:52 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Mandrake RPMs
Compiler:          gcc (GCC) 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk) 
OS:                Linux

When I start my computer, kded is using up as much of the cpu as it can. I am unable to start konqueror (it hangs).

Once I kill kded, I get a message that says: "The KDE mountwatcher is not running. Please activate it in the Control Center->Kde Components->Service Manager, if you want to use the devices:/ protocol". Additionally, the hung konqueror instances start up.

I can then start kded manually, and it does not exhibit the same behavior.
Comment 1 hichem 2004-11-02 22:43:44 UTC
Problem is related in pluging usb external devices like usb key or usb storage disk.
Disabling mountwatcher /usr/share/services/kded/mountwatcher.desktop  resolves the problem but still get the message that says: "The KDE mountwatcher is not running. Please activate it in the Control Center->Kde Components->Service Manager, if you want to use the devices:/ protocol"which is obviously logical now.
Comment 2 hichem 2004-11-03 18:25:25 UTC
Reproduced this issue on MDK 10.1 with KDE 3.2.3
Comment 3 Greg Martyn 2004-11-03 21:20:52 UTC
So it's in both 3.2.3 and 3.3? Hmm..

Just reporting that your workaround fixes the problem on my computer. Too bad we have to disable the devices:/ protocol to do it though!
Comment 4 Greg Martyn 2004-11-11 15:41:32 UTC
Tried the Mandrake 10.1 Community (even though I'm running 10.1 Official) rpms of KDE 3.3.1 from their club-contrib. Looks like this has been fixed.
Comment 5 Greg Martyn 2004-11-23 21:47:06 UTC
Forgot to mark as resolved.