Created attachment 157180 [details] log SUMMARY On Plasma Wayland, when I resume from sleep mode, I get no output on my monitor and the only way to workaround the problem is to kill kwin or restart the computer. STEPS TO REPRODUCE 1. Use Plasma Wayland 2. Put system into sleep mode, not hibernate 3. Resume from sleep mode 4. No output is shown OBSERVED RESULT When resuming from sleep, I have nothing on my screen and my monitor says their is no output EXPECTED RESULT The lock screen should show up like normal when resuming from sleep mode SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 (With backports ppa) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NAVI22 Manufacturer: ASUS ADDITIONAL INFORMATION I am using a hdmi monitor that is connected to a custom built pc with an amd graphics card
> Mar 11 10:24:36 sams-pc-rig kwin_wayland_wrapper[3195]: kwin_core: Applying KScreen config failed! > Mar 11 10:24:36 sams-pc-rig kwin_wayland_wrapper[3195]: kwin_wayland_drm: Atomic commit failed! Invalid argument > Mar 11 10:24:36 sams-pc-rig kwin_wayland_wrapper[3195]: kwin_wayland_drm: Presentation failed! Invalid argument > Mar 11 10:24:36 sams-pc-rig kwin_wayland_wrapper[3195]: kwin_wayland_drm: Failed to find a working setup for new outputs! It would be good to know what config KWin is failing to apply. Please add > QT_LOGGING_RULES="kwin_*.debug=true" to /etc/environment, reboot, make the bug happen again and upload the log again. A dmesg output with drm debug logging enabled (https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues) would be very helpful as well
Created attachment 157197 [details] Kernel dmesg log Contains log from dmesg
Created attachment 157198 [details] systemd log Contains log from systemd-journald
It appears that on the upcoming Kubuntu 23.04, the issue seems to be fixed. I tested using the daily images of Lunar Lobster. This suggests that it is either an old kernel causing the issue or a distro issue that has been fixed.
Yay! Thanks for following up.