https://bugs.kde.org/show_bug.cgi?id=452627
--- Comment #3 from Michael Hamilton <mich...@actrix.gen.nz> --- (In reply to Kai Uwe Broulik from comment #2) > Thanks for your effort! You may restart plasmashell (Type "plasmashell > --replace" into krunner) to reload the notification system. Thanks, that makes dealing with this much easier. > I wonder if there could be a race between the notification being added to > the model and us returning the ID. But it's single-threaded, so the signal > about the notification is emitted, the notification added, and only then the > function returns the ID. Some kind of race might play a role. My desktop does raises quite a few notifications. I used the notificatifications system to keep me alerted on background activity and email filtering. I've written an application to filter the journal and raise notifications (https://github.com/digitaltrails/jouno). That can raise bursts of notifications, but it does not update them. I've written another one to watch for CPU and memory hogs and raises notifications when a process exceeds specified limits (https://github.com/digitaltrails/procno). I recently added the ability to periodically update notifications with ongoing consumption. Testing this new feature lead me to raise this bug. I also added notification-actions, if they are enabled at the same time as notification-updates, similar problems occur, it could just be the same issue, miss-association of ID's, causing actions not to fire. Both the above applications are self contained scripts, with fairly basic PyQt+Dbus dependencies, so you're welcome to use them for testing should they be of any help. > > Does the notification system completely break once in corrupt state? i.e. > will replacing any notification fail after that or just once or just > specific ones? Once it's gone off the rails, it seems to stay broken, same pattern recurs: two notifications instead of one, with the second one updating. It's less common but sometimes I think that the second notification may not be appearing at all. -- You are receiving this mail because: You are watching all bug changes.
