Bug 515464

Summary:	Plasma Notifications with Critical severity level never expire
Product:	[Plasma] plasmashell	Reporter:	Eduard Korchmar <korchmar.eduard>
Component:	Notifications	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	minor	CC:	kde, olib141
Priority:	NOR
Version First Reported In:	6.5.91
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Eduard Korchmar 2026-02-03 16:26:29 UTC

SUMMARY
As caused by this code, notifications with Critical urgency level do not expire:
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libnotificationmanager/notification.cpp?ref_type=heads#L496

STEPS TO REPRODUCE
notify-send -u critical -t 1000 "I am here forever"

OBSERVED RESULT
Notification is here forever until manually closed.

EXPECTED RESULT
Expiration timer of 1000 milliseconds is respected, regardless of critical severity.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.91
KDE Frameworks Version: 6.22.0
Qt Version: 6.11.0
Kernel Version: 6.18.7-arch1-1 (64-bit)

ADDITIONAL INFORMATION
Here is example of application bug report, which generates Critical notifications through DBus and expects them to still expire in set time:
https://github.com/wezterm/wezterm/issues/7553

It may be weird of application  to designate a notification as critical and then set expiration timer for it. However, it is also weird for a notification manager to override applications' intent in such an opaque way.

Comment 1 Oliver Beard 2026-02-03 23:53:49 UTC

I believe it's more an application issue — a critical notification is something that requires the user intervention as soon as possible, regardless of whether they are currently away from their computer.

An application should not flippantly issue critical notifications.

As such, I do not believe a change at our end is justified and I am closing the issue as RESOLVED INTENTIONAL.