SUMMARY Notifications often dont disappear automatically. When clicking on the "close" button, or the "settings" button, it often doesnt respond for some clicks. STEPS TO REPRODUCE 1. Get a notification on Fedora KDE 2. wait for it to autoclose, it may not 3. try to close it by clicking the button OBSERVED RESULT Windows dont autoclose. The button doesnt react some times, you need to press it three times often. EXPECTED RESULT Normal counter integration. This may be something bigger, as auto-hiding the taskbar also doesnt work. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland
Is the button visibly becoming clicked, but nothing happens? Or is nothing happening visibly, such that the notification looks like it's hung? What GPU do you have?
(In reply to Nate Graham from comment #1) > Is the button visibly becoming clicked, but nothing happens? Or is nothing > happening visibly, such that the notification looks like it's hung? > > What GPU do you have? The alarm windows are frozen, clicking on them once doesnt do anything, until it works and the button gets pressed
Okay no, the button is clickable and gives feedback but no action until 2. press I have Graphics Processor: Mesa Intel® HD Graphics 4000 (internal graphics) Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz I also never have transparency anywhere for some reason. I experience inconsistent behavior on multiple things, the auto-disappearing panel works currently, as well as the auto-disappearing notifications. This was a log when I pressed the x, but it worked first time. But some times the messages dont auto-disappear and the panel stays there, its the same behavior, as if something would freeze. Feb 06 19:56:08 fedora plasmashell[4864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x7dd3b074d400) QQmlContext(0x7d30caafb220) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml") Feb 06 19:56:08 fedora plasmashell[4864]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x7dd3b074d400) QQmlContext(0x7d30caafb220) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml") Feb 06 19:56:08 fedora plasmashell[4864]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML SelectableLabel: Binding loop detected for property "implicitWidth" Feb 06 19:56:08 fedora plasmashell[4864]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML SelectableLabel: Binding loop detected for property "implicitWidth" Feb 06 19:56:08 fedora plasmashell[4864]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML SelectableLabel: Binding loop detected for property "implicitHeight"
I got no journalctl log from the error, where could I look otherwise? I could reproduce the freezing notification windows again.
Thanks for the info.
I have this problem with Wayland and X11. It also doesn't matter what graphics I'm on (Intel or Nvidia). It worked fine and without any updates, it stopped working. Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: XPS 15 9510
I'm also seeing those messages in the logs when it happens: 25.05.23 15:11 plasmashell org.kde.plasma.notifications: Trying to invoke default action on notification 27 which doesn't have one 25.05.23 15:12 dbus-daemon apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" member="ActivationToken" name=":1.23" mask="receive" pid=4362 label="snap.slack.slack" peer_pid=3045 peer_label="unconfined" 25.05.23 15:46 plasmashell file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:106:15: QML MouseEventListener: Binding loop detected for property "height" 25.05.23 16:03 plasmashell Could not find the Plasmoid for Plasma::FrameSvgItem(0x55ee19faddb0) QQmlContext(0x55ee126a5250) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml") 25.05.23 16:10 plasmashell org.kde.plasma.notifications: Trying to configure notification 35 which isn't configurable
Good find. Maybe an AppArmor configuration issue where it's blocking the DBus close action? Does the issue go away if you disable AppArmor? However that's probably not related to Henning's original issue, as Fedora is in use there and Fedora uses SELinux, not AppArmor.
(In reply to Nate Graham from comment #8) > Good find. Maybe an AppArmor configuration issue where it's blocking the > DBus close action? Does the issue go away if you disable AppArmor? > > However that's probably not related to Henning's original issue, as Fedora > is in use there and Fedora uses SELinux, not AppArmor. I tried it. I did a `sudo aa-teardown`, the messages are still not disappearing. But I couldn't disable AppArmor completely since the snapd service is depending on it. I did not find a correlation from a specific log message to when the message isn't disappearing. I had the snap apps in mind, but it's also not that. Always after three clicks on the close button, it disappears. I gladly give up the investigation if there would be a workaround :) is there a config/cache/file I could reset that could potentially make the problem go away?
No idea, sorry. Can you submit a new bug report for this so we're not hijacking Henning's issue?
Henning, is it still happening for you on Fedora 38 with Plasma 5.27?
Yes this is still happening. As I said I think this is dependend on some timer not being activated, windows not being focused or something. It is irregular, while the autohide taskbar is always only hiding after clicking on it. The notifications 70% or the time autohide, sometimes they dont. It is happening on --- Software --- OS: Fedora Linux 38.20230609.0 (Kinoite) KDE Plasma: 5.27.5 KDE Frameworks: 5.106.0 Qt: 5.15.9 Kernel: 6.3.5-200.fc38.x86_64 Compositor: wayland --- Hardware --- CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx RAM: 13.5 GB GPU: AMD Radeon Vega 8 Graphics Video memory: 2048MB
I just did a full reset of the plasma-org.kde.plasma.desktop-appletsrc. It was still happening to me. I'm using the Fokus applet (https://store.kde.org/p/1308861/). After removing it, it didn't happen anymore (so far). Is it possible that this is linked to that applet?
Yep. Henning, are you also using the 3rd-party Fokus widget?
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!
I reported the problem to the fokus author. He fixed the problem by avoiding direct api usage of the kde notifications api and opting to a python lib (https://gitlab.com/divinae/focus-plasmoid/-/commit/6b77f7a9eeedf77498258915d7bd75a570300b3b). Since the solution got copied from a calendar widget, it seems to me like a common notification api problem. Anyway, the problem is fixed, thanks to all developers involved