Bug 435249 - Notification timeout in OSD messages is not adhered if urgency is set to critical
Summary: Notification timeout in OSD messages is not adhered if urgency is set to crit...
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.20.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-02 07:05 UTC by boris.sh.1983+kde.bugzilla
Modified: 2021-04-06 00:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description boris.sh.1983+kde.bugzilla 2021-04-02 07:05:23 UTC
SUMMARY


STEPS TO REPRODUCE
1. notify-send -t 1000 -u critical "cirtical message but should dissapear in 1 seconds"
2. wait 1 second


OBSERVED RESULT

OSD is still on after 1 second

EXPECTED RESULT

OSD is gone after 1 second.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Debian Gnu/Linux bullseye
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Mode other than critical work as epxected.

such as notify-send -t 1000 -u normal "non cirtical message but should dissapear 
in 1 seconds"
Comment 1 Nate Graham 2021-04-06 00:51:10 UTC
Yes that's intentional. Critical notifications never time out and have to be explicitly acknowledged by the user as a matter of policy. If a notification is deemed unimportant enough that the user can miss it without issue, it's by definition not critical, and you shouldn't mark it as critical. :)