Bug 282490 - kded daemons never exit, stuck in zombie/defunct state
Summary: kded daemons never exit, stuck in zombie/defunct state
Status: RESOLVED DUPLICATE of bug 236490
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 17:48 UTC by Craig Magina
Modified: 2012-04-15 00:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Magina 2011-09-21 17:48:08 UTC 
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

After a period of time running kde, there are a bunch of kded processes in a defunct state.

Reproducible: Always

Steps to Reproduce:
Just run the desktop for a while, although it might require suspensions to actually cause the issue.

Actual Results:  
A bunch of defunct/zombie kded daemons.

Expected Results:  
No defunct/zombie kded daemons.

OS: Linux (x86_64) release 3.0.0-11-generic
Compiler: gcc
Comment 1 Craig Magina 2011-09-21 19:16:43 UTC 
It has nothing to do with suspension. I rebooted my system and over the course of time that has passed since I submitted this bug there have been created a bunch of kded zombie/defunct processes. What data can I gather to help debug this issue?
Comment 2 Christoph Feck 2011-09-21 20:14:01 UTC 
You could follow this document to find out which kded4 module is responsible: http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
Comment 3 Christoph Feck 2011-09-25 23:38:54 UTC 
Additionally, please verify if this is a duplicate of bug 236490.
Comment 4 Christoph Feck 2011-10-14 09:43:05 UTC 
If you can provide the information requested in comment #2 and/or comment #3, please add it.
Comment 5 Will Stephenson 2012-04-15 00:44:42 UTC 
Ubuntu and no further information, let's assume it was a dupe.

*** This bug has been marked as a duplicate of bug 236490 ***