-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank screen after powering of monitor #7744
Comments
I have a similar issue with a 165Hz FreeSync monitor: Sentey MS2711 I can reproduce this 100% of the time with:
I had to use big timeout of 60 seconds or so, since sleeping for 1 second wasn't enough to reproduce the issue. I think this has to do with the monitor going to "power-save" after a few seconds. The sway log doesn't show any error. |
And, I forgot to mention, a workaround for this issue is to switch back and forth TTYs. In my system the graphical session is on TTY1, so switching to TTY2 and then TTY1 turns the monitor on again. Here are the debug logs: (The handling of the |
This is probably video card issue, let me guess you have AMD? and it's using DisplayPort? |
Yes, I have an AMD Radeon RX 5600 connected through DisplayPort. |
@itaranto Yeah I've been having issues with my 5700 and Vega laptop, there's many bug reports on the tracker. I think the Display core rewrite they did like a year ago was a mistake, it's been nothing but trouble. |
I found this issue which seems to be related. |
I'm having the same issue on Intel Iris graphics and Apple XDR display. |
Narrowed it down a bit: installed GNOME side by side on the same kernel, and GNOME handles it correctly under wayland. So it's not any boot or kernel params, seems like wlroots or sway issue. |
Are you able to reproduce on Sway+wlroots latest commits? |
@emersion yes, with a new issue: can't use the screen anymore in full res. I've noticed improvements in hot plug behavior, as in the first couple of times the monitor would come back up. Here's get_outputs output in the broken state ATM on sway HEAD:
Tried turning it on with |
I've been having the same issue, sometimes I can reproduce it with When disabling the display via swayidle, ~90% of the time I encounter this problem, 100% of the time if I lock the screen in swayidle too, using swaylock. It looks like the monitor tries to turn on, but it stays black for a short period and turns off again. The logs looks kinda weird: When sway receives the power on command:
For some reason, the display is disables right after:
Heres the full log, its kinda noisy: |
Sway Version:
Debug Log:
https://gist.github.com/gregath/84f6f187bf790d969e441e77bb94b987
Configuration File:
https://gist.github.com/gregath/84f6f187bf790d969e441e77bb94b987
Description:
Power off monitor and power it back on and the screen will be blank. It happens when changing inputs on the monitor as well, but not when turning dpms off for 5 seconds.
The text was updated successfully, but these errors were encountered: