SUMMARY Notifications don't auto hide after update. STEPS TO REPRODUCE 1. Trigger a notification popup 2. Popup displays 3. Popup doesn't auto hide according to system setting of 5 seconds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4
What kind of notification is this, or does it affect all of them? Persistent notifications (e.g. notify-send foo bar -t 0) will no longer auto-hide in the new system.
Yeah, the key piece of information is what notification you're seeing this problems with. All, or some, and which ones?
(In reply to Kai Uwe Broulik from comment #1) > What kind of notification is this, or does it affect all of them? Persistent > notifications (e.g. notify-send foo bar -t 0) will no longer auto-hide in > the new system. KDE connect messages will sometimes autohide and other times not. It will show the same message multiple times too. I've noticed it most with the plasma integration plugin for Chromium and KDE connect notifications. Another application is PIA (Private Internet Access) has a notification that comes up when you connect, on startup the message doesn't auto close but if I start it after booting the message auto hides.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
New information was added with comment #3. Changing status for inspection.
Same on x86-64 box running Fedora 31 (Qt 5.12.5, KDE Plasma 5.16.5, KDE Frameworks 5.61.0). Which notifications? Mostly Konsole ones as it is source of >90% notifications in my system. Most of notifications hide. Some stay until clicked so I often have hours old notification popups when I start using computer in the morning.
I have the same issue on Plasma 5.18.1 on Manjaro (testing). I've had it for some time. E.g. I just had a kmail notification that did not auto-dismiss. When I hovered over it, the circular timer started again but it did not dismiss. And when I want to dismiss it, it requires TWO clicks on the close button. Yet, when I issue a "notify-send testing" command, the notification auto-dismisses. So it only happens sometimes. It does not seem to matter what the application is--it happens also with Firefox and other applications.
Someone just let me know about this bug on Reddit, as I have had this same phenomenon with Pushbullet notifications sent from Chrome on Manjaro. All other Chrome notifications seem to time out appropriately, but not those being generated by the Pushbullet extention within Chrome, which require manual dismissal to remove. So that might help narrow down the problem to reproduce it and track the issue. Also, in retrospect, the PIA notification mentioned above has the same problem as well. Thank you!
This seems to be an issue with specific programs and not with KDE. For example, the same issue happens with Pushbullet for Chrome on KDE and Cinnamon, but does not happen on these desktops with PB for desktop standalone, not does it happen with Pushbullet add-on for Firefox on these desktops. I'd contact pushbullet's for Chrome developers to submit a bug report.
This seems to be an issue with specific programs and not with KDE. For example, the same issue happens with Pushbullet for Chrome on KDE and Cinnamon, but does not happen on these desktops with PB for desktop standalone, nor does it happen with Pushbullet add-on for Firefox on these desktops. Also - notifications from other Chrome extensions on KDE (and Cinnamon) time-out and diseapper correctly. I'd contact pushbullet's for Chrome developers to submit a bug report.
@MikeYo: good to know that Konsole is no longer part of KDE. On my system it was the main reason why I disabled notifications.
Marcin, which Konsole notifications? How to reproduce?
(In reply to MikeYo from comment #12) > Marcin, which Konsole notifications? "Bell in 'Shell #1'" ones. > How to reproduce? Any notification from Konsole worked iirc. Or maybe most. Do not remember as it was painful and boring. Now I do not have any notifications and life looks brighter. Do not plan to enable them back.
Cannot reproduce. Konsole's bell notifications time out properly for me. I suspect what's going on here is that the notification system started making critical notifications stay always visible5, which revealed that various apps were abusing the critical status for clearly non-critical information. In this case, the apps' developers should be contacted. Closing in the absence of a reproducible case or any information that the Plasma notification system is at fault here. Please file bugs on the individual apps whose notifications don't time out when you think they should. Thanks!
Nate, I also suspected it may have something to do with critical notifications, but aren't critical notifications on KDE suppose to stay longer, but not permanently? I mean, on Mint Cinnamon that has the same notifications issue with PB for Chrome, there is a setting for that (https://forums.linuxmint.com/viewtopic.php?t=311789), it is 4s vs 10s, not permanent. Isn't there a similar setting in KDE?
There's a setting for how long non-critical notifications appear on-screen, but critical notifications remain visible until the sending app specifically revokes them.