Bug 455448

Summary:	System freeze/crash when turning off and on monitor on wayland
Product:	[Plasma] kwin	Reporter:	fuomag
Component:	multi-screen	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	fuomag, nate, thebellenik, xaver.hugl
Priority:	NOR	Keywords:	regression, wayland-only
Version First Reported In:	5.25.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description fuomag 2022-06-16 22:24:54 UTC

SUMMARY

I have two monitors. I was using wayland. Turning off and on the monitor on the right made the system freeze and unresponsive and I had to reboot


STEPS TO REPRODUCE
1. have two monitors and use wayland
2.  turn off monitor on the right
3.  turn on monitor on the right
4. system freezes

OBSERVED RESULT
system freezes

EXPECTED RESULT
system should not freeze (like it does on x11)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.25.0
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

Comment 1 Nate Graham 2022-06-17 19:34:03 UTC

Is this a regression in Plasma 5.25 as compared to 5.24?

Comment 2 fuomag 2022-06-17 19:35:34 UTC

(In reply to Nate Graham from comment #1)
> Is this a regression in Plasma 5.25 as compared to 5.24?

Yes, in plasma 5.24 I had another bug, right display got black background and no right click for setting it after turning it on and off, but the system did not freeze/crash

Comment 3 Nate Graham 2022-06-17 19:40:22 UTC

By any chance are you using a multi-GPU system?

Comment 4 fuomag 2022-06-17 19:43:13 UTC

(In reply to Nate Graham from comment #3)
> By any chance are you using a multi-GPU system?

Single GPU, NVIDIA 2070S

The right click bug I had was #353975 btw, which does not seem to happen anymore (probably due to the freeze, but at least apparently the background remains. Can't right click unfortunately)

Comment 5 fuomag 2022-06-21 18:49:26 UTC

Still happening on 5.25.1-1, now I cannot even move the mouse anymore

Comment 6 Nate Graham 2022-09-08 22:04:57 UTC


*** This bug has been marked as a duplicate of bug 450488 ***