Bug 461168

Summary:	On 16:9 4K screen, resolution 1920x1080 not offered under wayland
Product:	[Plasma] KScreen	Reporter:	Ralf Jung <post>
Component:	common	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate, xaver.hugl
Priority:	NOR
Version:	5.26.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:	5.26.3
Sentry Crash Report:

Description Ralf Jung 2022-10-29 16:49:44 UTC

SUMMARY
My laptop has a 4k screen with max resolution of 3840 x 2160. However I usually prefer to run it in full HD resolution, 1920 x 1080. When using an X11 session, kscreen offers to configure the screen with that resolution, but under Wayland it does not -- I can pick 1920 x 1200, or 2560 x 1440, but I cannot select 1920 x 1080.
sy

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 6.0.0-2-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
Memory: 31,2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics P530
Manufacturer: LENOVO
Product Name: 20ENCTO1WW
System Version: ThinkPad P50

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2022-11-01 14:02:54 UTC

Interesting, I have a screen with the same resolution and aspect ratio (on a 14" ThinkPad X1 Yoga), and the combobox offers me that resolution on Wayland.

Comment 2 Nate Graham 2022-11-01 14:03:28 UTC

I'm using Fedora rather than Debian, so maybe some system library is newer on my system and that makes it work better?

Comment 3 Ralf Jung 2022-11-01 15:38:26 UTC

On IRC I was told that this should fix my problem: https://invent.kde.org/plasma/kwin/-/merge_requests/3138.

Comment 4 Nate Graham 2022-11-01 15:44:04 UTC

Ok cool. Can you check in Plasma 5.26.3 to see if the problem's fixed?

Comment 5 Ralf Jung 2022-11-01 15:50:55 UTC

Once it is packaged in Debian I can check that, yeah...

Comment 6 Ralf Jung 2022-12-31 09:00:48 UTC

Looks like unfortunately this bug is back, but in a worse form: https://bugs.kde.org/show_bug.cgi?id=463655