https://bugs.kde.org/show_bug.cgi?id=407881
Kai Uwe Broulik <k...@privat.broulik.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Version Fixed In| |5.16.0
Latest Commit| |https://commits.kde.org/pla
| |sma-workspace/17f1834e98ae0
| |61226b10b572c4aeebcaca042bc
--- Comment #7 from Kai Uwe Broulik <k...@privat.broulik.de> ---
Git commit 17f1834e98ae061226b10b572c4aeebcaca042bc by Kai Uwe Broulik.
Committed on 29/05/2019 at 11:47.
Pushed by broulik into branch 'Plasma/5.16'.
[Notifications] Spawn new notification if one to replace doesn't exist
Since the Notification Server knows nothing about what notifications were sent,
it tells us a notification was replaced and
uses the ID supplied by the application. Only in the model we then realize it
didn't exist.
This means we will potentially reuse the notification ID sent by the
application as we just increment a counter.
However, in practice I haven't encountered this issue before (maybe we just
never noticed?) but I think this is an
acceptable workaround.
FIXED-IN: 5.16.0
Differential Revision: https://phabricator.kde.org/D21474
M +2 -0 libnotificationmanager/notificationsmodel.cpp
https://commits.kde.org/plasma-workspace/17f1834e98ae061226b10b572c4aeebcaca042bc
--
You are receiving this mail because:
You are watching all bug changes.
