Created attachment 136152 [details] kwin Crash No 1 Firefox Since the release of Plasma 5.21.0, I constantly get Kwin crashes when using Firefox, Thunderbird and NoMachine. Still present in Plasma 5.21.1. STEPS TO REPRODUCE 1. Use Firefox (in my case with enabled WebRender), Thunderbird or drag elements around in a running NoMachine remote desktop 2. Kwin crashes 3. Compositing mode gets disabled and the fallback 2D mode gets enabled SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Frameworks Version: Plasma 5.21.1 Qt Version: 5.15.2 kwin_x11: ../libepoxy/src/dispatch_common.c:858: epoxy_get_proc_address: Zusicherung »0 && "Couldn't find current GLX or EGL context.\n"« nicht erfüllt. [English: Not fulfilled] Application::crashHandler() called with signal 6; recent crashes: 1 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwin_x11 path = /usr/bin pid = 9100 KCrash: Arguments: /usr/bin/kwin_x11 --crashes 1
Created attachment 136153 [details] Kwin Crash No 2 Thunderbird
Created attachment 136154 [details] Kwin Crash No 3 Nomachine
Can you post the full backtrace please? When kwin crashes, there should be a sad icon in the system tray. If you click that icon, you should see the backtrace.
Sadly, there is no backtrace icon. How can I manually get this log? Does strace report the same?
Created attachment 136170 [details] Kwin Crash No 3 - strace with Firefox
Can I provide any other info? I’m using a Radeon RX 5700 XT, recent kernel version 5.11. Is my strace log sufficient?
Problem solved by deleting Kwin config files in ~/.config and /.local/share and a reconfiguration afterwards. Possible reasons for this bug: I was using the Kwin-Lowlatency fork during Plasma 5.20’s lifetime. It wasn’t compatible with Plasma 5.21, so I had to switch back to the mainline Kwin. The Lowlatency fork could theoretically have made harmful modifications to my config. Other possibilities: This Kwin config was very old and grown since I think the Plasama 4 days. Plasma 5.21’s Kwin could have introduced something my config was in conflict with. There were some other minor problems like missing chrome/frame in the standard transparent program switcher or missing "X" buttons in the Exposé/'present window' effect, these are also gone now with the reset.