Bug 482684 - Issues after wake up from power save
Summary: Issues after wake up from power save
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen, wayland
Depends on:
Blocks:
 
Reported: 2024-03-07 10:50 UTC by Lorenz Hoffmann
Modified: 2024-08-09 03:46 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lorenz Hoffmann 2024-03-07 10:50:14 UTC
SUMMARY
***
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
***

I have a two-monitor setup. The system went into power-save and turned the monitors off. After wake-up, the image froze and one monitor was not turning on again. After some time, I could interact with the primary monitor again.

STEPS TO REPRODUCE
1. Have two monitors connected
2. Wait until the energy save mode turn them off
3. Move the mouse to turn the screens on again

OBSERVED RESULT
System is frozen, and one screen remains turned off

EXPECTED RESULT
Both monitors should turn on again... and the system should not freeze. 

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 2080/PCIe/SSE2

ADDITIONAL INFORMATION
Primary monitor on the left is connected with display port, the other one on the right with HDMI.
Comment 1 Lorenz Hoffmann 2024-03-07 12:31:50 UTC
Actually, this happens only if the system was locked, not when just turning off the screens. System didn't freeze the second time this happened
Comment 2 major-mayer 2024-05-15 14:19:37 UTC
I think I have a similar issue, now that Manjaro updated to Plasma 6.0.4.
Most of the time when I put my system into sleep and wake it up again, my second display is black until I manually turn it off and on again.
Then after a few seconds it connects again.
This was never an issue for me with Plasma 5.
Also in my case, the primary display is connected via DP and the secondary via HDMI to an AMD graphics card.
Any logs that would help?
Comment 3 jd4dvc0js 2024-05-16 12:14:03 UTC
This exact same issue started happening with me after a system-wide upgrade that updated KDE Plasma to 6.0.4.

I have 3 monitors, 2 of them DVI and one HDMI. After sleep, the HDMI one doesn't wake up anymore. I have to disconnect the power chord and reconnect again.

I had to disable "Turn off screen" in Energy Settings to prevent this from happening.
Comment 4 Zamundaaa 2024-07-10 15:41:23 UTC
Please attach the output of drm_info, once for when the output is working correctly, and once for when it's not displaying anything
Comment 5 Bug Janitor Service 2024-07-25 03:46:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2024-08-09 03:46:41 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.