-
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
DPMS Off on Focused Output Only #4419
Comments
I did some review of the log and wanted to generate a new one where the DPMS off command was sent from within the sway instance that opened when running sway -d 2> ~/sway.log, i'm not sure which log version will be more helpful but both are in the gist posted above. |
The logs appear to be from a nested sway session running in another wayland compositor. dpms is not supported on the wayland backend. If you are using DRM, which it sounds like, please generate the debug log with a sway session running on DRM and not a nested session. |
Updated the gist with a fresh log, DP-1 was the only output that successfully turned off |
Might be tied to this issue swaywm/wlroots#1768 reported 13 days ago by @emersion |
Should be fixed by the revert in #4434 and swaywm/wlroots#1781 |
Thanks for the fix, tested and working great again. I'm adding a new log to the gist link in my original post in case there is anything valuable. |
This reverts commit 01f9038 and re-applies commit ee5f98a. Updates: swaywm#1640 (Atomic output updates issue) See also: swaywm#1762 (Atomic output updates original PR) See also: swaywm#1780 (Issue caused by atomic output updates) See also: swaywm/sway#4419 (Issue caused by atomic output updates) See also: swaywm#1781 (Revert PR)
This reverts commit 01f9038 and re-applies commit ee5f98a. Updates: #1640 (Atomic output updates issue) See also: #1762 (Atomic output updates original PR) See also: #1780 (Issue caused by atomic output updates) See also: swaywm/sway#4419 (Issue caused by atomic output updates) See also: #1781 (Revert PR)
This reverts commit 01f9038 and re-applies commit ee5f98a. Updates: swaywm#1640 (Atomic output updates issue) See also: swaywm#1762 (Atomic output updates original PR) See also: swaywm#1780 (Issue caused by atomic output updates) See also: swaywm/sway#4419 (Issue caused by atomic output updates) See also: swaywm#1781 (Revert PR)
Sway Version:
sway version 1.1-rc1-91-g90d8a4df (Aug 3 2019, branch 'master')
Debug Log:
https://gist.github.com/Elevate08/ef5f8b6344ccda62c9ef403f252aeb28
Configuration File:
https://github.com/Elevate08/dots/blob/master/.config/sway/config
Using swayidle to turn the displays off after x time. Only one display is turning off - It appears to be whichever display is the "active" or focused display at the time of running the swaymsg "output * dpms off" command.
What also happens during this time is it appears to remove the output from the configuration as well (workspace moves to one of the active monitors) (See Line 1056, maybe?)
I've installed everything from the AUR repo on a fresh Manjaro install yesterday. Also, for what it's worth i'm running a RX 590 GPU (One DP, 2 HDMI)
The text was updated successfully, but these errors were encountered: