You are not logged in.
Hello everyone,
few months I have some problem with X11/GDM. After few hours of my computer usage monitors won't turn off (black screen then energy saving mode) when I lock desktop or wait 5 mins to automaticly screen blanks . In Settings -> Power -> Power Saving I have set Blank screen to 5min. Only solution is to reboot computer. I have 2 DELL U2415 monitors chained with DP cable and connected via miniDP to workstation.
Output of
xset -q
is:
xset -q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 0
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/TTF,built-ins
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is On
$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "2" # DRI3 is now default
#Option "AccelMethod" "sna" # default
#Option "AccelMethod" "uxa" # fallback
EndSection
$ uname -a
Linux vlado-desktop 5.13.13-arch1-1 #1 SMP PREEMPT Thu, 26 Aug 2021 19:14:36 +0000 x86_64 GNU/Linux
$ sudo lshw
Is there any workaround or fix for this? When I switch from Xorg session to Wayland, everything works except presenting in google meet (I need it for my work)
Thanks
Last edited by vladimir.darak (2021-09-11 07:12:57)
Offline
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
Something™ set this to "0" what mans "never"
Assuming that's your desktop session, trying to handle this itself.
1. Can you "xset dpms force off"?
2. If so:
systemd-inhibit --list
qdbus org.freedesktop.ScreenSaver /ScreenSaver # check whether your implementation is willing to list the inhibitors
Also
Only solution is to reboot computer.
Sure that a re-login doesn't do?
Offline
Hello,
thanks for response!
I don't know how gnome works with DPMS but
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
Is always 0. Even when blanking and energy saver mode working.
1. yes, command works. Monitors are blanked and wakes up when I move mouse or press key on keyboard
2. current output
WHO UID USER PID COMM WHAT WHY MODE
NetworkManager 0 root 445 NetworkManager sleep NetworkManager needs to turn off networks delay
UPower 0 root 1239 upowerd sleep Pause device polling delay
GNOME Shell 1000 vlado 1864 gnome-shell sleep GNOME needs to lock the screen delay
Telepathy 1000 vlado 1920 mission-control shutdown:sleep Disconnecting IM accounts before suspend/shutdown... delay
vlado 1000 vlado 2067 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block
vlado 1000 vlado 2067 gsd-media-keys sleep GNOME handling keypresses delay
vlado 1000 vlado 2068 gsd-power sleep GNOME needs to lock the screen delay
7 inhibitors listed
but actually everything works.
Yes, only solutions is reboot. I can logout and change session type from Xorg to Wayland. Then blanking start working again.
Currently I'm testing fallback mode for intel graphic card:
$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "2" # DRI3 is now default
#Option "AccelMethod" "sna" # default
Option "AccelMethod" "uxa" # fallback
EndSection
Offline
Only sleep and hibernation are inhibited, not DPMS.
You want to check this as well as "xset dpms force off" when things do *not* work.
I don't think it's related to the ddx driver (settings), esp. not if restarting X11 doesn't resolve it.
Offline
I tested
xset dpms force off
even when blanking do not work but command works correctly. I tried to restart GDM when blanking not work and after that, all things work again
Last edited by vladimir.darak (2021-09-03 06:11:39)
Offline
You didn't check for the inhibitors, did you?
It's not related to your GPU for sure, though.
Offline
$ systemd-inhibit --list qdbus org.freedesktop.ScreenSaver /ScreenSaver
WHO UID USER PID COMM WHAT WHY MODE
NetworkManager 0 root 445 NetworkManager sleep NetworkManager needs to turn off networks delay
GNOME Shell 1000 vlado 1864 gnome-shell sleep GNOME needs to lock the screen delay
Telepathy 1000 vlado 1920 mission-control shutdown:sleep Disconnecting IM accounts before suspend/shutdown... delay
code 1000 vlado 68675 code sleep Application cleanup before suspend delay
vlado 1000 vlado 2067 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block
vlado 1000 vlado 2067 gsd-media-keys sleep GNOME handling keypresses delay
vlado 1000 vlado 2068 gsd-power sleep GNOME needs to lock the screen delay
7 inhibitors listed.
Looks like "vlado 1000 vlado 2067 gsd-media-keys" blocks everything
Offline
% systemd-inhibit --list
% qdbus org.freedesktop.ScreenSaver /ScreenSaver
Those are two commands. But afaics gnome-screensaver doesn't expose inhibitors anyway.
It blocks the power keys, that's not related to screen locking/dpms. Is this while the screen won't turn off?
See https://bbs.archlinux.org/viewtopic.php … 4#p1991134 - some™ process might go rogue for both of you (though that would break the DPMS you forced in #5 pretty much immediately)
Offline
Currently monitor won't turn of automatically after period from settings. Same problem when I lock teh computer.
systemd-inhibit --list
WHO UID USER PID COMM WHAT WHY MODE
NetworkManager 0 root 448 NetworkManager sleep NetworkManager needs to turn off networks delay
GNOME Shell 1000 vlado 1190 gnome-shell sleep GNOME needs to lock the screen delay
Telepathy 1000 vlado 1251 mission-control shutdown:sleep Disconnecting IM accounts before suspend/shutdown... delay
code 1000 vlado 128852 code sleep Application cleanup before suspend delay
vlado 1000 vlado 1413 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block
vlado 1000 vlado 1413 gsd-media-keys sleep GNOME handling keypresses delay
vlado 1000 vlado 1415 gsd-power sleep
$ qdbus org.freedesktop.ScreenSaver /ScreenSaver
signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface_name, QVariantMap changed_properties, QStringList invalidated_properties)
method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name)
method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name)
method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value)
method QString org.freedesktop.DBus.Introspectable.Introspect()
method QString org.freedesktop.DBus.Peer.GetMachineId()
method void org.freedesktop.DBus.Peer.Ping()
signal void org.freedesktop.ScreenSaver.ActiveChanged(bool arg_0)
method bool org.freedesktop.ScreenSaver.GetActive()
method uint org.freedesktop.ScreenSaver.GetActiveTime()
method uint org.freedesktop.ScreenSaver.GetSessionIdleTime()
method uint org.freedesktop.ScreenSaver.Inhibit(QString application_name, QString reason_for_inhibit)
method void org.freedesktop.ScreenSaver.Lock()
method bool org.freedesktop.ScreenSaver.SetActive(bool e)
method void org.freedesktop.ScreenSaver.SimulateUserActivity()
method uint org.freedesktop.ScreenSaver.Throttle(QString application_name, QString reason_for_inhibit)
method void org.freedesktop.ScreenSaver.UnInhibit(uint cookie)
method void org.freedesktop.ScreenSaver.UnThrottle(uint cookie)
Offline
Did you see the thread I linked in #8 and do you get likewise spurious input?
The other thread was resolved by updating linux 5.13.12 to 5.13.13
Offline
Many thanks! I found the issue. Problem is with my web camera. When I pull out USB from my computer and push it back, all works fine. Currently I'm on kernel 5.13.13-arch1-1
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline