#1035075 gnome-shell: After lock, screen is black, but not blanked (no powersave)

Package:
gnome-shell
Source:
gnome-shell
Description:
graphical shell for the GNOME desktop
Submitter:
Manuel Bilderbeek
Date:
2023-04-28 21:21:02 UTC
Severity:
normal
#1035075#5
Date:
2023-04-28 21:04:47 UTC
From:
To:
Dear Maintainer,

After installing Debian testing on my new PC recently, I noticed that my
monitor isn't powered off after the screen is blanked by GNOME. This worked
fine on my previous PC. What happens after manually locking (or after the 15
minutes of idleness):
- screen goes black and backlight goes off (as expected)
- after 12 seconds, the backlight goes back on (screen stays black). This is
  unexpected and prevents the monitor from going into power save mode.

I saw this in the journalctl output, after manually locking the screen at 22:54:00:
Apr 28 22:54:00 creator gnome-shell[2362]: INFO extension.js::disable(21) disabling Network Stats
Apr 28 22:54:00 creator gnome-shell[2362]: INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
Apr 28 22:54:20 creator gnome-shell[2362]: [FREON] Unable to find smart devices: GLib.SpawnError: Uitvoeren van dochterproces <E2><80><98>null<E2><80><99> is mislukt (Bestand o>
Apr 28 22:54:20 creator gnome-shell[2362]: [FREON] Unable to find nvme devices: GLib.SpawnError: Uitvoeren van dochterproces <E2><80><98>null<E2><80><99> is mislukt (Bestand of>
Apr 28 22:54:20 creator gnome-shell[2362]: loading default theme (Adwaita)
Apr 28 22:54:20 creator gnome-shell[2362]: INFO extension.js::enable(15) enabling Network Stats
Apr 28 22:54:20 creator gnome-shell[2362]: DEBUG net/DeviceMonitor.js::_loadDevices(100) 2 - lo:   13179     100    0    0    0     0          0         0    13179     100    0>
Apr 28 22:54:20 creator gnome-shell[2362]: DEBUG net/DeviceMonitor.js::_loadDevices(100) 3 - eno2:       0       0    0    0    0     0          0         0        0       0   >
Apr 28 22:54:20 creator gnome-shell[2362]: DEBUG net/DeviceMonitor.js::_loadDevices(100) 4 - eno1: 43905861   59280    0 3920    0     0          0      4763  6798980   40510  >
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceMonitor.js::_getIPAddress(188) No IP addresses found for device 'eno2'
Apr 28 22:54:20 creator gnome-shell[2362]: DEBUG net/DeviceMonitor.js::_updateDefaultDevice(142) default gateway: eno1
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceModel.js::init(49) init - eth0 - Tue Apr 11 2023 20:05:33 GMT+0200 (Midden-Europese zomertijd)
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceModel.js::init(49) init - eno2 - Fri Apr 28 2023 00:07:19 GMT+0200 (Midden-Europese zomertijd)
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceModel.js::init(49) init - eno1 - Fri Apr 28 2023 00:07:19 GMT+0200 (Midden-Europese zomertijd)
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceModel.js::init(49) init - enx1ce192b2e7c2 - Tue Apr 11 2023 20:05:34 GMT+0200 (Midden-Europese zomertijd)
Apr 28 22:54:20 creator gnome-shell[2362]: INFO net/DeviceModel.js::init(49) init - wlp7s0 - Thu Apr 13 2023 00:00:56 GMT+0200 (Midden-Europese zomertijd)
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed
Apr 28 22:54:20 creator gnome-shell[2362]: Failed to query filesystem: method Gio.File.query_filesystem_info_async: At least 4 arguments required, but only 3 passed

That means, nothing special. At 22:54:20 I unlocked the system again, when I saw that the backlight turned back on.

This behaviour happens both under Wayland and Xorg.

I also tried to report this upstream, as I found something similar, but I'm not
sure if it's the same thing, but I'll mention it here for reference:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4773

As I wrote there:
Board: ASUSTeK COMPUTER INC. ProArt X670E-CREATOR WIFI
Processor: AMD Ryzen 9 7950X 16-Core Processor (25/97/2)
I'm using the GPU from the Ryzen.

If there is anything I can do to help to analyze this or if there is a
workaround, please let me know.

Kind regards,
Manuel Bilderbeek

#1035075#10
Date:
2023-04-28 21:17:04 UTC
From:
To:
Dear maintainer,

I just thought of the following test (running Wayland):

busctl --user set-property org.gnome.Mutter.DisplayConfig
/org/gnome/Mutter/DisplayConfig org.gnome.Mutter.DisplayConfig
PowerSaveMode i 1; sleep 30; busctl --user set-property
org.gnome.Mutter.DisplayConfig /org/gnome/Mutter/DisplayConfig
org.gnome.Mutter.DisplayConfig PowerSaveMode i 0

That does turn off the screen for 12 seconds, but then it's going back
on. And 18 seconds later the command finishes...

Looks like the same 12 seconds I saw when locking.