Bug 433794

Summary:	kwin compositor crash recovery handling is overly annoying
Product:	[Plasma] kwin	Reporter:	Jason Straight <j.straight-kde>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	r2b2x3+kdebug
Priority:	NOR
Version First Reported In:	5.21.1
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jason Straight 2021-03-01 14:18:07 UTC

Running nvidia on my laptop, when I disconnect external monitors, or suspend/resume, the compositor often crashes. I get that that probably can't be helped, but recovery is more annoying than it needs to be.

Currently, I have to go into compositor settings and click the re-enable detection error message (ctrl-alt-f12 doesn't work). Then I have to change a setting twice. Once to get it to turn compositor back on, and once to change the setting back to where I want it to be, now that the compositor is enabled and working again.

It would be nice if simply clicking the re-enable would turn the compositor back on, with current settings.

I tried to figure out if there was a way to do this automatically with dbus and set a hotkey for it, but couldn't figure out what needed to be done, if it's even possible.

Operating System: Manjaro Linux
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.11.2-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: GeForce RTX 2060/PCIe/SSE2

Comment 1 Jason Straight 2021-09-01 19:59:22 UTC

After someone on reddit said, "Lemme guess, you're using an Arch distro." and continued that all these kinds of problems seem to be on Arch systems, I tried OpenSuSE TW, and was surprised that the problem did not exist there. I've been TW since then [many months] without this issue.

Tried Arch on an external SSD a few weeks back and the issue was still there.

No clue what Arch does differently. Just FYI for anyone else finding this.

Comment 2 David Edmundson 2023-09-06 10:38:23 UTC

This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.