https://bugs.kde.org/show_bug.cgi?id=440051
Bug ID: 440051
Summary: Reusing replaces_id after expiry does not work
Product: plasmashell
Version: 5.22.3
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Notifications
Assignee: k...@privat.broulik.de
Reporter: kroot.pa...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
Ever since the update to 5.22.x, notifications that reuse a replaces_id by
setting it equal to a notif_id from notification that has already expired (aka,
timed out and no longer visible), are not rendered.
STEPS TO REPRODUCE
1. Use https://github.com/phuhl/notify-send.py to create a notification:
notify-send.py Body -r 1234 -a Appname
2. Wait for the notification to timeout
3. Resend the notification, with a modified body
notify-send.py NewBody -r 1234 -a Appname
OBSERVED RESULT
Modified notification does not show up.
EXPECTED RESULT
Modified notification should show up as if it were a new notification (with the
default timeout).
SOFTWARE/OS VERSIONS
Linux: Manjaro
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
This scenario (reusing replaces_id after expiry) is not specified by the spec,
but virtually every notification server behaves as expected, by creating a new
notification.
I guess the buggy behaviour was introduced in the commits
https://invent.kde.org/plasma/plasma-workspace/-/commit/ee822faf1c86844b6bcac8f1c55cc152de2c376e
and
https://invent.kde.org/plasma/plasma-workspace/-/commit/5890aa64f939285486f3d64caf46de13a8e2dd62
Shouldn't the notifications be getting cleaned up on expiry?
--
You are receiving this mail because:
You are watching all bug changes.
