https://bugs.kde.org/show_bug.cgi?id=452627
Bug ID: 452627
Summary: The notification system can become corrupted -
notifications fail to update
Product: frameworks-knotifications
Version: 5.93.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: mich...@actrix.gen.nz
CC: kdelibs-b...@kde.org
Target Milestone: ---
Created attachment 148165
--> https://bugs.kde.org/attachment.cgi?id=148165&action=edit
Notifications test bash script
SUMMARY
The notification system can become corrupted.
I'm not exactly sure how. Possibly by raising too multiple notifications at the
same time. Possibly by updating a notification too soon. Possibly by using
ID's that weren't generated by the notification system.
Once corrupted, updating existing notifications does not work: the initial
notification displays and returns an id, for example 61, but updating that id
results in the message "org.kde.plasma.notifications: Trying to replace
notification with id 61 which doesn't exist, creating a new one. This is an
application bug!", a new notification appears above the original one, it
returns the same ID, and this new notification can then be successfully updated
in place. So I see to notifications on the screen, and only the second one
updates.
Once corrupted, the only way I know to reset notifications is to logout and
login, then updates work as expected, the initial notification returns and ID,
and updates to the ID change this initial notification.
STEPS TO REPRODUCE
1. Unsure exactly how to force the system into an error state.
2. i) Raise a notification and record it's ID
ii) Run attached shell script with starting ID 0, and two or more repeats,
for example:
% bash test_notifications.sh 0 3
3. Check whether you only see one notification and it gets updated the correct
number of times, if not the fault has
occurred
OBSERVED RESULT
When the notification system is corrupted, you will see two notifications: the
initial one, and one for the first update. The one for the first update will
actually update for the rest of the iterations.
EXPECTED RESULT
I would always expect to see one notification and it would update for the set
number of iterations.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20220411
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
Can the notification subsystem be reset/restarted without a logging out? That
would make testing much easier.
--
You are receiving this mail because:
You are watching all bug changes.
