https://bugs.kde.org/show_bug.cgi?id=486514
--- Comment #2 from Fabio C. Barrionuevo <bna...@gmail.com> --- (In reply to Nate Graham from comment #1) > Ew, this would be a bug with the code for the notifications themselves. > > Some questions to help us narrow it down: > 1. Do you observe it happening with any other notifications from other apps? No. I can't remember any other notification type with the same problem. Furthermore, the only notifications I remember seeing frequently are from Spectacle when I take a screenshot, and they have no issues. > 2. Can you make it happen with any permutations of running `notify-send` > with various options? I tried and was unable to reproduce the issue using notify-send . > 3. Does it happen in the Wayland session too, or only on X11? Currently, I only use X11 since Google Chrome has erratic behavior on Wayland, and my daily work doesn't give me time to have the patience to wait for it to stabilize. I tried to reproduce the problem in Wayland by simply logging out of the X11 session and logging into the Wayland session. However, the notification no longer appears, probably because the action that launches it has already been executed and/or has been marked as read (if such a thing exists). Since the notification only appears when I have cold-booted the computer and there is some new update to install, over the next few days, I will first try starting the computer in a Wayland session to see if the problem also occurs on Wayland. -- You are receiving this mail because: You are watching all bug changes.
