Created attachment 159212 [details] Screenshot - screen configuration SUMMARY When returning from "suspend", the monitors do not turn on or return with low resolution (640x480). Wayland does not allow changing resolution (attachment). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). 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. Manually suspend the computer. 2. Wait for the suspension process to finish (front panel LED flashes). 3. Press any key to wake up the computer. OBSERVED RESULT Screens go black after manual suspend. One of the screens returns with 640x480 resolution after returning from automatic suspend (when automatic splint shutdown is not active). If the screen turns off automatically (before automatic suspend) the monitor video returns with adequate resolution (1600x900) EXPECTED RESULT Screens turn on after computer resumes from sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OS: Kubuntu 22.04.2 LTS x86_64 Kernel: 5.19.0-42-generic KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION To view any content, you must force restart with the power button or remove and reinsert the monitor cable. I installed the amd package for the gpu but the problem remained. https://www.amd.com/en/support/graphics/amd-radeon-6000-series/amd-radeon-6600-series/amd-radeon-rx-6600
I'm afraid Plasma 5.24 is unfortunately no longer eligible for support or maintenance from KDE. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. Please update to Plasma 5.27 by upgrading to Kubunty 23.04. If you need support for Plasma 5.24, please contact your distro, who bears the responsibility of providing support for older non-LTS releases. If this issue is still reproducible in Plasma 5.27, feel free to re-open this bug report. Thanks for understanding!
Thanks for the clarification. Those who found this page, here is the link of the issue on the Ubuntu bug hub. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020709