[wayland] KWin crashes when I Alt+Tab

[Cannon_Palms]

I’ve recently been working to move my desktop PC from X11 to Wayland. It was going quite smoothly until I hit this particular issue. I’ve had the skills to debug and fix everything that’s come up prior, but when we reach GDB, I’m out of my depth.

With a 100% rate of occurrence, when I Alt+Tab, KWin crashes, dumps its core, and restarts. When it restarts, most of my applications are no longer running. Sometimes Konsole will still be running, strangely, but certainly everything else I’ve tried is lost upon this crash.

I am not allowed to upload the GDB file that the debugging documentation specifically intructed me to record, though, so I’ll need direction there.

I can’t upload text files either, so I can’t share share information about my system through qdbus!

Community? Does this belong here? What’s the standard for uploading files?

[bedna]

That sounds serious and you should probably create a bug report at bugs.kde.org

But you can also send the info here by copy pasting (unless it is insane amounts) you can press this button: (press the cogwheel to get the drop down)

And then paste the log. (in text)

[Cannon_Palms]

Thank you!

The guide suggests that if you don’t know it to be a bug, to start with the forums. Bit confusing, all of it.

Thank you for the direction. I’ll head off to the bug tracker and link back here for posterity.

[bedna]

@Cannon_Palms

The guide suggests that if you don’t know it to be a bug, to start with the forums. Bit confusing, all of it.

I mean, yes, that is correct, but I assumed you knew it to be a KDE related crash and not something else on the system.

Post the log like I showed earlier and people could take a look!

[Duha]

@Cannon_Palms

The guide suggests that if you don’t know it to be a bug, to start with the forums. Bit confusing, all of it.

If it crashes it is a bug :D. Regular people probably can’t read backtraces so its probably better to report crashes to the bug tracker.

Are you using polonium by any chance?

[deftdawg]

@Cannon_Palms I now have this exact same issue, along with all the icons in my launcher bar bunching up over the “start” button… did you end up creating a bug for it or finding a solution to it?

[deftdawg]

At least as far as the alt-tab problem, if I uncheck(disable) Task Switcher Visualizations I no longer have the problem with Kwin crashing, but I still have this for my launcher

This stuff all used to work a few system updates ago (I don’t restart with each update), so not sure how it broke exactly.

[deftdawg]

Seems all visual effects crash kwin, i.e. dragging a window to the top of the screen to maximise also crashes kwin

[deftdawg]

The problem is this setting in ~/.config/kdeglobals:

[QtQuickRendererSettings]
SceneGraphBackend=software

I have no idea how that how it was set, but once I remove it, save and force a crash, I can once again alt+tab and snap windows with visualisation animations without crashing kwin.

EDIT: looks to be the same as this - caused by a crash and automatic fallback, how annoying…

On error KDE6 X11 switched to the Software-Renderer - how to reverse?

I had the software renderer permanently kick in after some plasmashell errors under X11. A logout or reboot doesn’t reset it. This seems similar to the “compositor” switch in KDE5 which could be reversed via the Systems Settings GUI. Similar to KDE5 compositor warning dialog, I think there was a brief dialog flash up mentioning the software rendering was activated. But it lacked any OK button, so it just flashed up without me being able to fully read it. I couldn’t find a switch to re-enable…

[digitaltrails]

@deftdawg

I have no idea how that how it was set

As mentioned the fallback is automatic - outside your control.

I noticed because I have a login startup job that checks the X11 compositor, which can also fallback to software. The job raises a notification. I’m not sure checking the compositor will always catch SceneGraphBackend=software, but I’ve now added a check for that too. Here’s the script I’m currently using:

#!/bin/bash
#set -x
# Wait for desktop to settle down
sleep 30

compositor_enabled=$(qdbus-qt5 org.kde.KWin /Compositor org.kde.kwin.Compositing.active)

if [ "$compositor_enabled" != "true" ]
then
     notify-send -a "Check Compositor" -t 0 -i dialog-error.png 'Hardware -> Display and Monitor -> Compositor is disabled!'
fi

if grep -q 'SceneGraphBackend=software' ~/.config/kdeglobals
then
     notify-send -a "Check kdeglobals"  -t 0 -i dialog-error.png 'Warning ~/.config/kdeglobals SceneGraphBackend=software'
fi

[deftdawg]

@deftdawg

QtQuickRendererSettings

Thanks, I’ve opened a bug 486078 – Automatically enabling software rendering causes KWin to crash on all visual effects (alt+tab, maximise, snap window)

I don’t think Plasma should do what it’s doing silently and then just leave users to figure it out on their own…

I’ll use your script in the meantime, though with a change to #!/usr/bin/env bash for the magic line to get it to run on NixOS.

[mingshi2333]

it occupies again, and the resolve is

[QtQuickRendererSettings]
SceneGraphBackend=hardware

if you have graphics card