Bug 453199

Summary:	Wayland: Disconnecting and reconnecting monitor causes it to copy screen scale from other monitor
Product:	[Plasma] KScreen	Reporter:	Katalin Rebhan <me>
Component:	common	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate, notmart, xaver.hugl
Priority:	NOR
Version First Reported In:	5.24.4
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	5.26
Sentry Crash Report:

Description Katalin Rebhan 2022-04-29 16:28:21 UTC

SUMMARY
I have a dual-monitor setup with a 150% scale monitor and a 100% scale monitor. Whenever the screens turn off due to inactivity (or lose connection in any way including unplugging), recently most of the time the 100% scale monitor will be set to 150% scale when I come back. Sometimes it's also the other way around, the 150% scale monitor being set to 100%.

I don't remember exactly what update this was introduced in, just that it was a recent one, most likely either Plasma 5.24.3 -> 5.24.4 or Frameworks 5.92.0 -> 5.93.0.

STEPS TO REPRODUCE
1. Set up two monitors with different screen scale
2. Disconnect/turn off one of the monitors
3. Plug it back in

OBSERVED RESULT
Screen scale will be copied from the other monitor

EXPECTED RESULT
Screen scale stays as it was set before disconnecting

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.8
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.14.21-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 23.4 GiB of RAM
Graphics Processor: AMD Radeon RX Vega

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2022-11-08 23:00:09 UTC

Can you paste the output of `kscreen-doctor -o` when it's working properly, and then again immediately after the bug happens? Thanks!

Comment 2 Katalin Rebhan 2022-11-09 10:59:12 UTC

(In reply to Nate Graham from comment #1)
> Can you paste the output of `kscreen-doctor -o` when it's working properly,
> and then again immediately after the bug happens? Thanks!

I can't reproduce it anymore right now, with 5.26.2. I assume it was fixed as part of something else.

Comment 3 Nate Graham 2022-11-09 15:04:14 UTC

Great, thanks!