Some notifications remain visible, even though the timeout has elapsed. Hovering the notification with the mouse restarts the timer (and the vertical progress bar), but the notification won't disappear until I manually dismiss it, clicking the red X-button.
I have the same problem, this happens for me with notifications from KDE Connect, and with notifications from Firefox (Whatsapp Web). Other notifications do disappear after the timeout.
Related : 369041
Trying again as can't edit : bug 369041
I'm added a comment on here , although I think either this or bug 369041 should be marked as duplicate. I am seeing this as well. Info Center gives: Operating System: Fedora 33 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.10-200.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz Memory: 23.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Its not consistent , if I clear all notifications sometimes things sent with timeout do go away, sometimes things get stuck and then they all pile up. This even happens with kdialog with --passivepopup <msg> 3 If I clear all notifications, then e.g. "/usr/bin/kdialog --passivepopup "%subject from %sendername" 3" works again and messages stop piling up. I do wonder if its Firefox google chat pinned tab that is not timing out that then causes everything to pile up behind it.
*** Bug 369041 has been marked as a duplicate of this bug. ***
*** Bug 390784 has been marked as a duplicate of this bug. ***
My observation has been that low-priority notifications do the timer animation and *do* go away (which seems correct). Normal-priority notifications do the little timer animation around the close button but *do not* go away (which seems broken). Critical-priority notifications do not show the animation and do not go away (which seems correct). The change to me seems to be the way normal notifications don't hide after the timing animation like they used to. I've only really started noticing it over the last month or so in the newer plasma packages for Ubuntu Jammy. It's annoying because so many apps (Teams, Flameshot, etc.) use normal-level notifications. Unfortunately we can't just completely disable notifications from something like Teams... or we won't see an "answer this call" pop-up if someone calls you. In addition to having 'normal' priority notifications autohide after timeout, it would be great to have extra options in the notification configuration such that the *user* can decide if they want each priority to autohide (or not) after their own configurable times. And, of course, if it could be overridden on a per-app basis then all the better.
Hello, I'm getting this issue using compiled plasma desktop 5.25.0 in Kubuntu 21.04 Kubuntu comes with 5.24.4 and notifications are fine. Operating System: Kubuntu 21.10 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2 Any one else has notice this regression? Thanks
I have this issue in KDE Neon fully updated. Doing kdialog with --passivepopup holissssssssssss 3 has the issue, as well as brave/chrome notifications. Restarting the system solves the issue till... till something happens and breaks. Sorry I can't give more details on the conditions for this to happen, I have this issue for more than a year, sometimes it disappears, then is back. It happens with Xorg using intel or nvidia (as default, not prime) Can I do something to shed more light on this @Kai Uwe Broulik ?
Using Plasma 5.25.3 solved the problem for me.
Can reproduce on 5.26
Cannot reproduce with `kdialog with --passivepopup holissssssssssss 3` in Plasma 5.27.5 on Wayland.
*** Bug 465409 has been marked as a duplicate of this bug. ***
Closing as I can't reproduce this any longer with Plasma 6.
In Fedora 41, KDE Plasma 6.2.2 through 6.2.4, I have been able to replicate the issue with any PWA installed with Firefox (PWA extension), Edge, and Chrome. The notifications pop up in the bottom right and pile up until you hit the close button on each one. I have changed the notification hideout settings from 5, down to 4, back to 5 to see if it was a weird configuration issue, but that doesn't resolve it. I need to keep the notifications enabled for work since I am using both the Teams, and Outlook PWA. It is a minor annoyance, but just letting everyone know that it still pops up in 6.*. I can send more details or set up a RDP/Teamviewer session if needed for troubleshooting.
I may have jumped the gun on this; after changing the timeout settings for notifications, they appear to disappear after a few seconds. It seems more than 5, but they still disappear. The weird thing is that there isn't a progress indicator like there usually is with notifications, but it's working, so I will leave it at that.
This is still reproducible on 6.5.1 using Teams PWA on Chrom*/Edge. If someone quickly sends several messages, one of the notifications will invariably stick and not go away.
Created attachment 187516 [details] screenshot Here's a screenshot of two Teams notifications not going away at all. Usually it will be just one of them that sticks. This is on 6.5.4
Do those notifications have a timeout progress bar, and when it disappears, the notifications remain visible? Or do they have no timeout progress bar at all?
They don't have a timeout progress bar at all.
In that case, you're not experiencing the original issue that Christian was. In your case what's most likely happening is that Teams itself set the HTML "requireInteraction" flag that keeps the notification open until interacted with.