Created attachment 160224 [details] display resolution error in X11 session Running Debian sid/unstable booting kernel 6.3.0-2 display settings thinks that I am using Wayland, when actually in X11. If I reboot using kernel 6.3.0-1 then display settings correctly identifies that I am in X11. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot using latest Debian unstable kernel 6.3.0-2 and into X11 session 2. Go to Settings -> Display and Monitor 3. Cannot change resolution and there is an info / exclamation icon that reports "Using unsupported resolutions was possible in the Plasma X11 session, but they were never guaranteed to work and are not available in the Plasma Wayland session." OBSERVED RESULT Cannot change resolution and there is an info / exclamation icon that reports "Using unsupported resolutions was possible in the Plasma X11 session, but they were never guaranteed to work and are not available in the Plasma Wayland session." EXPECTED RESULT Change display resolution that was available in kernel 6.3.0-1 SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Operating System: Debian GNU/Linux 12 Kernel Version: 6.3.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6700M Manufacturer: LENOVO Product Name: 82UH System Version: Legion 7 16ARHA7
Created attachment 160225 [details] display resolution working correctly Display resolution selection working correctly with kernel 6.3.0-1 in X11 session.
Can confirm this on plasma 5.27.6 and kernel 6.4.2-1
Upgrading debian kernel to 6.4.4-1 resolved issue. $ uname -a Linux jsola1 6.4.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.4-1 (2023-07-23) x86_64 GNU/Linux No idea what changes were made between debian kernel 6.3.0-2 to 6.4.0-1, but glad the bug was fixed.