Created attachment 131017 [details] KDE Info Center OpenGL When Compositor set to set to use OpenGL, both 2.1 or 3.0, GUI "freezes" after a while. Especially when working with Firefox. Freeze means mouse moves are still possible, but no clicks etc. possible/accepted anymore. No window changes, like refreshed graphs etc. No / never any freezes with Xrender. STEPS TO REPRODUCE 1. open plasma settings, all settings, display and monitor, Compositor 2. set output module to OpenGL, 2.1 or 3.0. 3. work some time, 1-15 minutes. OBSERVED RESULT Freeze, as described. EXPECTED RESULT NO freeze :-) SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.2 (available in About System) KDE Plasma Version: Plasma 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Hardware is ZBOX nano CI320 with an Intel Celeron N2930 and Intel HD Graphics. KDE Info Center OpenGL Info appended as screenshot
Can you switch to a VT (i.e control+alt+f2 and get a terminal) ?
yes, that's my "rescue path" to systemctl isolate multi-user.target and systemctl isolate graphical.target to get my machine back to a working state, avoiding hard reboots.
Requested information was added with comment 2; changing status.
I may be experiencing the same problem. When it happens: - I can still move the mouse pointer. - Mouse clicks and drags are ignored. - Nothing other than the mouse pointer changes on-screen. - Keyboard input still works (shortcuts, typing text, etc.) but since no screen updates happen, it looks like nothing is happening. - Switching virtual consoles Control+Alt+F8/F7 does not clear the problem. I cannot reproduce it on demand, but when it happens, it's always when an application disables the compositor, such as when a video player switches to full screen. I can regain control of my desktop by manually re-enabling the compositor with Shift+Alt+F12. However, once the bad state has been triggered once, every subsequent attempt to disable the compositor (either by an app or with Shift+Alt+F12) freezes the desktop again. If I reboot, the compositor can once again be switched off or on without any trouble, until the problem appears again. That might take hours or days.
Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 6.0.0-0.deb11.6-amd64 Graphics Processor: AMD Radeon RX 480 Graphics
I (In reply to Forest from comment #4) > I may be experiencing the same problem. When it happens: > > - I can still move the mouse pointer. > - Mouse clicks and drags are ignored. > - Nothing other than the mouse pointer changes on-screen. > - Keyboard input still works (shortcuts, typing text, etc.) but since no > screen updates happen, it looks like nothing is happening. > - Switching virtual consoles Control+Alt+F8/F7 does not clear the problem. > > I cannot reproduce it on demand, but when it happens, it's always when an > application disables the compositor, such as when a video player switches to > full screen. > > I can regain control of my desktop by manually re-enabling the compositor > with Shift+Alt+F12. > > However, once the bad state has been triggered once, every subsequent > attempt to disable the compositor (either by an app or with Shift+Alt+F12) > freezes the desktop again. > > If I reboot, the compositor can once again be switched off or on without any > trouble, until the problem appears again. That might take hours or days. I have been experiencing this exact same issue under X11 since I upgraded my KDE neon laptop to Plasma 5.27. Never happened under 5.26, but it's happening almost every day. It seems to trigger after a long period of time on its own, without any user interaction. I can be away from my computer for awhile and come back and find that it appears to be dead except for a movable cursor. Disabling the compositor with Shift+Alt+F12 is what gets my session usable again, but the Plasma panels are non-responsive though I see that plasmashell is still running with htop. I've been trying to find a pattern for what causes it, and the I've noticed that plasma-systemmonitor is the only program that seems to be in an unresponsive state when it happens and needs to be forcibly killed. Correlation? Maybe. I was thinking it was some byproduct of the OpenGL drivers, so I installed the Obiaf PPA to get the latest Mesa, but there was no change. Since this is such an odd bug, I don't even know how to describe it to file it as a bug. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics
*** This bug has been marked as a duplicate of bug 342326 ***