SUMMARY I have experienced random freezes of the whole UI which persist until I switch to a tty and kill KWin with "kill -9". The freezes appear to be related to showing notifications. Nothing appears in logs except for the following: May 04 12:16:07 Sleipnir plasmashell[3299972]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PlayerController.qml:92: TypeError: Type error May 04 12:16:07 Sleipnir plasmashell[3299972]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5652c7f4bdd0) QQmlContext(0x5652bf68f6c0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notification> May 04 12:16:07 Sleipnir plasmashell[3299972]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5652c7f4bdd0) QQmlContext(0x5652bf68f6c0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notification> Sometimes the freeze doesn't happen all at once, but Plasma's widget pop-ups appear as black rectangles and then the whole UI freezes. Bringing up KRunner doesn't work (it accepts a couple of keystrokes, then freezes). In those cases I need to also restart the plasmashell process as it remains unresponsive even after restarting KWin. STEPS TO REPRODUCE 1. ? OBSERVED RESULT The whole UI freezes. EXPECTED RESULT There are no freezes (sorry, rather generic but it really can't be more specific than this...). SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION CPU: AMD Ryzen 5 2500U GPU: AMD Radeon Vega 8 Mesa: 22.2.5 I am using multiple screens: the laptop's one is duplicated to an external screen with the same resolution (1920x1080), plus another screen (2560x1440), both connected through a USB-C dock.
I also have a problem with freezes in some apps (I'm using X11 + AMD + Nvidia setup, the external screen is connected to Nvidia, the internal screen is connected to AMD GPU). Usually one one windows freezes and the problem can be solved by either of: restarting KWin, restarting the frozen up or moving the app to the other screen and back. I think it might be some upstream bug in GPU driver's in PRIME Sync implementation.
Riccardo, is this on X11 or Wayland?
Whoops, I forgot to mention, sorry. It's X11. I updated Mesa from version 22.2.5, which is the one provided by the Neon repos, to version 23.1.0, which is provided through Kisak's PPA, and this seems to have fixed the issue as I haven't experienced it ever since. I would therefore argue that the problem lies in some incompatibility between KWin and Mesa 22.2.
Could be... or just a Mesa bug all on its own. It can do that. Regardless, I'll let the KWin developers take it from here
This sounds exactly like symptoms of https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674
(In reply to Zamundaaa from comment #5) > This sounds exactly like symptoms of > https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 I wonder if this should be treated as a packaging issue for Neon, given the distro only offers Mesa 22.2.5 which has this issue. Maybe it could be bumped to 22.3 or 23.0 to avoid it. Any thoughts on this?
Probably. Feel free to submit a bug report about it for Neon.
I have just had the exact same issue, but now I have kernel 6.5.2 installed together with Mesa 23.1.7 which should not be affected by the issue mentioned in the linked freedesktop bug report. Any idea what the problem might be? In this case I am using the laptop's own screen and an external screen connected through the laptop's own HDMI port.