dbus method calls to "org.gnome.ScreenSaver.SetActive false" do not work properly
Affected version
Provide at least the following information:
- Debian 11 (Gnome3 w/Wayland). Untested on more up to date systems.
- gnome-shell 3.38.6-1~deb11u1 amd64 (latest for Debian 11 bullseye)
- Reproducible in Debian live environment (i.e. without extensions or user configuration)
- AMD A10-7800 CPU, integrated AMD graphics, ASUS A68 OEM motherboard
- HDMI and VGA monitors connected
Bug summary
Calling "org.gnome.ScreenSaver.SetActive false" causes all screens to wake (as expected), but a few seconds later all screens go blank again and do not come back on (unexpected).
Steps to reproduce
- Boot a Debian Live ISO. I used Debian 11.5 non-free live, but encountered the behaviour with an up to date Debian 11 install on the PC's SSD.
- Install sshd so commands can be entered remotely:
sudo apt update && sudo apt install -y openssh-server && sudo systemctl start sshd
- Record the ip address of the computer to assist in ssh access:
ip addr show
- From another computer, SSH into the PC running the Debian Live OS:
ssh user@IPADDRESS
- Start the screensaver:
gdbus call --session --dest org.gnome.ScreenSaver --object-path /org/gnome/ScreenSaver --method org.gnome.ScreenSaver.SetActive true
- Attempt (and fail?) to end the screensaver:
gdbus call --session --dest org.gnome.ScreenSaver --object-path /org/gnome/ScreenSaver --method org.gnome.ScreenSaver.SetActive false
- Watch the Debian Live PC's screen(s). They should turn on, then off again and stay off.
- Wiggle the mouse on the Debian Live PC. The screensaver should end normally.
What happened
The screensaver resumes after a few seconds of calling "SetActive false", rather than ending.
What did you expect to happen
I expected the screensaver to end permanently, just like what happens when mouse or keyboard input are detected.