Bug 207913

Summary: plasma notification tray gets flooded
Product: [Unmaintained] plasma4 Reporter: Ritesh Raj Sarraf <kde-bugs>
Component: notificationsAssignee: Rob Scheepmaker <rob>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra, notmart, plasma-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: plasma notification flood
knotify4 crash (incomplete) backtrace

Description Ritesh Raj Sarraf 2009-09-19 20:46:52 UTC 
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

This bug happens sometimes. Not always.

Also, this seems to be triggered with the combination of kontify and plasma notifications.

Seems like knotify internally crashes and then plasma simply queues up all the notifications. And then, later, when again for whatever reason knotify resumes/restarts, the plasma notifications start to flood like hell. And they also consume a lot of system resources.

In my case, I ran amarok. Once amarok started playing a song, knotify started playing notification sounds and plasma started flooding notifications. Eventually knotify crashed. But plasma notifications remained as it is. They did not go away.
Workaround then is to `pkill plasma-desktop; sleep 1; plasma-desktop`

I'm attaching a screenshot showing the plasma system notification flood. I will also paste the knotify crash, just in case it can give some pointers.
Comment 1 Ritesh Raj Sarraf 2009-09-19 20:47:51 UTC 
Created attachment 37071 [details]
plasma notification flood
Comment 2 Ritesh Raj Sarraf 2009-09-19 20:49:36 UTC 
Created attachment 37072 [details]
knotify4 crash (incomplete) backtrace

bts won't allow me paste it.
Comment 3 Dario Andres 2009-09-19 21:32:49 UTC 
The notifications "stack is too high" is reported here: bug 204867. However as this is also related to this KNotify problem I can't be really sure.
Thanks
Comment 4 Marco Martin 2009-11-28 16:11:37 UTC 

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