Display is not capable of DPMS After GNOME Wayland update

dpmsgnomewaylandxset

Seems like GNOME updated to Wayland which caused a few issues, the biggest is the periodic crash that brings you back to the login screen. Another issue that is hopefully easier to fix is that I can no longer put my display to sleep.

Before the update I was using this sh script bound to a shortcut:

sleep 1; xset dpms force off

After it produces the error below:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  147 (DPMS)
  Minor opcode of failed request:  6 (DPMSForceLevel)
  Serial number of failed request:  12
  Current serial number in output stream:  14

What is the correct way to put the display to sleep manually with Wayland?

Edit:

It appears that the DPMS does not work properly which is the reason for the error.

Check DPMS status:

xset -q

Result:

DPMS (Energy Star):
Display is not capable of DPMS

xset +dpms command does not enable it. It was working before the Gnome update so DPMS was supported. What could be the issue here?

Best Answer

So this here works for GNOME 3.24 Wayland:

put all displays in standby:

busctl --user set-property org.gnome.Mutter.DisplayConfig /org/gnome/Mutter/DisplayConfig org.gnome.Mutter.DisplayConfig PowerSaveMode i 1

Resume all displays:

busctl --user set-property org.gnome.Mutter.DisplayConfig /org/gnome/Mutter/DisplayConfig org.gnome.Mutter.DisplayConfig PowerSaveMode i 0

The command can be given over ssh, just in case ;) There does not seem to be a screen lock.

The GNOMErs decided to have gdm run a separate GNOME X session for screen lock, leading to a host of bugs and problems like what session is shown, what session is locked, what session has the keyboard. This is why blanking and screen lock are absent from the Wayland session.

It seems the World has yet to see a screen lock for Wayland.

Related Solutions

Turning off dual monitors with “xset dpms force off” does not work – why

What exactly are you trying to accomplish? For managing monitor usage you can/should use the randr extension where xrandr would be the weapon of choice in scripts.

xrandr -q shows all outputs of your computer and some info about connected monitors. To disable an output you would put something like xrandr --output=HDMI1 --off. In your case you have to replace "HDMI1" with whatever xrandr -q tells you your outputs are named. With your output disabled X does not use this monitor anymore (at all) and it will most likely enter a sleep state.

If you actually want the monitor to turn off, your problem is that xset does neither know nor care about how many monitors you have hooked up to your computer, because xset talks to Xservers, not their components and definetly not hardware. This means xset sends exactly one "dpms force off" request and that request is (processed and) sent to one of your monitors by the Xserver. I'd guess it sends it to your primary monitor, i.e. the one connected to the output that appears first in the list shown by xrandr -q. That's the same monitor your gnome panel lives on, if you're using gnome.

In effect I'd guess you have to issue your xset request twice. If that doesn't help immediately I'd assume you need to be explicit about the issue which of your attached monitors is primary and which is not.

xrandr allows you to set the primary output/monitor by the use of the --primary option. If your outputs are HDMI1 and HDMI2, I'd try:

xrandr --output HDMI2 --primary
xset dpms force off
xrandr --output HDMI1 --primary
xset dpms force off

Check the output of xrandr -q and write a script that turns off your monitors in the reverse order they are listet, that is bottom up. The reason for that is, that while (x)randr is supposed to be able to arbitrarily make outputs the default output I wouldn't/don't trust it to work that flawlessly, especially if there are closed source drivers involved. By working through your monitors in reverse order you turn off the "natural" primary monitor last and if things go wrong, having the "natural" primary monitor available is your best shot at having a fully functional Xserver.

Bash – Real GNOME Wayland session

I think you have to add that to .bashrc which also works for non-login shells.

Best Answer

Related Solutions

Turning off dual monitors with “xset dpms force off” does not work – why

Bash – Real GNOME Wayland session

Related Question