Bug 202835

Summary: many notifications from kwrite service reduce usability of notifiction service
Product: [Unmaintained] plasma4 Reporter: Martin Steigerwald <Martin>
Component: notificationsAssignee: Rob Scheepmaker <rob>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: many notifications through kwrite service.

Description Martin Steigerwald 2009-08-06 19:12:12 UTC 
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I use TuxOnIce for hibernation. During a hibernation and resume cycle some messages are generated. The KWrite service grabs those.

Sometimes I have one or two messages cause several lines are concatened. But sometimes I get one message by line even when a line is empty.

I then have to close each one of those individually.

My usual work-around for this annoyance is a pkill kwrited.
Comment 1 Martin Steigerwald 2009-08-06 19:13:06 UTC 
Hmmm, why is this reported against Kopete? I searched for plasma and selected notifications then.
Comment 2 Martin Steigerwald 2009-08-06 19:22:46 UTC 
Created attachment 35924 [details]
many notifications through kwrite service.

But I had up to 40 notifications for one hibernation cycle. Sometimes the notification stack goes beyond the upper border of the screen.

The notification system should collate or rate limit those.
Comment 3 Martin Steigerwald 2009-08-06 20:56:05 UTC 
Okay, it went to the Kopete developers as the search for plasma turned up a "Notifications" entry that further read something like "problems with the various notifications of kopete" or so. And I selected this cause I did not scroll to the side to see that additional text.

I think assign should be changed to plasma or knotify4. I am not sure which is more appriobate and seem to lack the bugzilla karma to do such an assignee change.

So please change assignee as approbiate.
Comment 4 Aaron J. Seigo 2009-09-03 11:13:11 UTC 

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