Bug 313922 - Plasma notifications are not removed from queue when closed
Summary: Plasma notifications are not removed from queue when closed
Status: RESOLVED DUPLICATE of bug 311413
Alias: None
Product: plasma4
Classification: Plasma
Component: notifications (show other bugs)
Version: 4.9.98 RC3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-26 14:39 UTC by Baokai Lei
Modified: 2013-02-08 20:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Baokai Lei 2013-01-26 14:39:44 UTC
Just noticed a bug in the plasma notification system (which has been rewritten for 4.10, as far as I got it).

Reproducible: Always

Steps to Reproduce:
1. Have a notification appear (e.g. copy a file large enough to make a notification appear.)
2. When the notification comes up, close it with the X in the upper right corner.

Actual Results:  
While the notification is closed when you click on the X in the upper right corner, it's *not* removed from the notification queue. You must click on the (i) next to the system tray to display the notification queue and then click on the X there to empty the notification queue, even if you got all notifications and dismissed them.

Expected Results:  
4.9 and previous behaviour: When you dismiss a notification by clicking on the X, it must *not* remain in the notification queue, but instead be removed from it. Only notifications that you missed and didn't dismiss by clicking on the X should stay in the notification queue, to be later displayed when you click on the (i).

Please fix this. It's quite bothersome when you open the notification queue and it shows *all* notifications, even those you got and dismissed, and you have to wade through the notifications to see which ones escaped your attention. Only notifications that you *didn't* dismiss should stay in the notification queue.
Comment 1 Jekyll Wu 2013-02-08 20:05:37 UTC

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