Bug 272538

Summary: Notification Helper is crashing Kded4
Product: [Unmaintained] kdelibs Reporter: incarus6
Component: kdedAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: crash CC: cfeck
Priority: NOR    
Version First Reported In: 4.6   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description incarus6 2011-05-05 15:22:59 UTC 
Version:           4.6 (using KDE 4.6.2) 
OS:                Linux

When booting with "Notification Helper" enabled kded4 is creating a zombie process (and eating more CPU then usually?), this doesn't happen when the notificiation helper is disabled.

Reproducible: Always

Steps to Reproduce:
1. Enable Notification Helper under Systemsettings
2. type "killall kded4"
3. type "kded4"
4. type "ps -u USERNAME | grep kded4", you will get something like:
 2838 pts/0    00:00:00 kded4
 2845 pts/0    00:00:00 kded4 <defunct>
5. Disable Notification Helper under Systemsettings
6. type "killall kded4"
7. type "kded4"
8. type "ps -u USERNAME | grep kded4", you will get something like:
 2853 pts/0    00:00:00 kded4

Actual Results:  
2838 pts/0    00:00:00 kded4
2845 pts/0    00:00:00 kded4 <defunct>

Expected Results:  
2853 pts/0    00:00:00 kded4
Comment 1 Christoph Feck 2011-05-05 15:58:35 UTC 
Are you using version 10.10? If yes, this might be fixed already, see bug 263790. If it is not fixed in latest 11.04 version, I suggest to report it downstream to Launchpad, as the Notification Helper is a Kubuntu-specific add on.
Comment 2 incarus6 2011-05-05 16:05:39 UTC 
(In reply to comment #1)
> Are you using version 10.10? If yes, this might be fixed already, see bug
> 263790. If it is not fixed in latest 11.04 version, I suggest to report it
> downstream to Launchpad, as the Notification Helper is a Kubuntu-specific add
> on.
I'm using 11.04. I found that bug on launchpad: https://bugs.launchpad.net/ubuntu/natty/+source/kubuntu-notification-helper/+bug/515138

thanks, I thought it's a KDE related bug