Bug 447427

Summary:	Switching to linux console and back turns the displays to black
Product:	[Plasma] kwin	Reporter:	auxsvr
Component:	platform-drm	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	atosser, nate, xaver.hugl
Priority:	NOR	Keywords:	wayland
Version:	5.23.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	6.1.0
Sentry Crash Report:

Description auxsvr 2021-12-23 13:00:34 UTC

SUMMARY
Switching to linux console and back displays just the mouse cursor and the monitor positions become incorrect. The Wayland session is still in progress and I use loginctl to kill it and start sddm.

STEPS TO REPRODUCE
1. Ctrl-Alt-F1 to switch to a Linux console.
2. Alt-F7 to switch to the Wayland session.

OBSERVED RESULT
The display on both monitors is black, only the mouse pointer appears. Also, the position of the monitors becomes incorrect and the backlight of the monitor other than the one with the mouse pointer is turned off.

EXPECTED RESULT
Resume the Wayland session as it was.

SOFTWARE/OS VERSIONS
Linux: 5.15.8
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
On Wayland with 2 monitors.

Comment 1 aTosser 2022-09-18 21:40:46 UTC

I also experience this on kwin_wayland. Bluetooth disconnects, eveything related to desktop vanishes and only a mouse and black background are present. Can not summon krunner or pull down a yakuake session.

Operating System: Gentoo Linux 2.8
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Kernel Version: 5.19.8-gentoo-dist (64-bit)
Graphics Platform: Wayland

Comment 2 Zamundaaa 2024-06-26 19:13:26 UTC

Do you still experience this issue in Plasma 6.1?

Comment 3 aTosser 2024-06-26 20:18:17 UTC

(In reply to Zamundaaa from comment #2)
> Do you still experience this issue in Plasma 6.1?

The session never dies completely like it used to but on occasion I still lose desktop interaction and the panel. Krunner still works so I just log out and back in again to fix the issue.

I cannot say if this behavior is related to the previous behavior.

Comment 4 Nate Graham 2024-06-26 22:18:45 UTC

Please open new bug reports for those issues. Thanks.