Bug 357750

Summary: With plasma5 a user can't set a notification as persistent
Product: [Plasma] plasmashell Reporter: gianogli <gianogli>
Component: NotificationsAssignee: Martin Klapetek <mklapetek>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: gianogli, plasma-bugs, yuxin.ma1989
Priority: NOR    
Version: 5.4.3   
Target Milestone: 1.0   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description gianogli 2016-01-09 17:16:14 UTC
Only a persistent notification is inserted into the Notification (history) widget. But an user can't set (or unset) the "persistent" option of a notification.

Reproducible: Always

Steps to Reproduce:
1. Open any configuration window to set the notifications
2. Chose an important event that should be notified to the user
3. Set the "Show a message in a popup"

Actual Results:  
The enabled notification for the chosen important event, is not persistent. (When the popup disappears, the Notifications widget into the taskbar contains only the "No new notifications" string)

Expected Results:  
I expect to have the possibility to choose myself (with an additional flag near the "Show a message in a popup" option or into the popup) such notifications are persistent for me.

If I lock the screen or if I go to talk to my colleagues for some seconds, when I come back to desktop or I unlock the screen I haven't any information about the important events (for me!) happened.
For instance I don't know if emails have arrived, if there was any bell on one of my console sessions, if backup script have finished successfully, ...

This behavior is very very very annoying and some KDE users could loose a lot of time to verify each time if some events are happened.
Comment 1 Martin Klapetek 2016-02-03 19:31:32 UTC
Thanks for the report

If a notification should be persistent or not, is up
to the application, as per the specification.

You should file a bug with the application if you
believe they are using the notifications wrong.

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