Monitor no longer shuts off when idle #5607
Comments
|
Same issue here on Arch Linux. Is it related to
from the July 16, 2018 update? |
|
It's likely related. As an added data point, I tried disabling in home streaming and have my steam controller turned off, and the display still won't sleep. |
|
This is still a problem as of today. I'm on a Gentoo machine with a blanking timeout of 10 minutes, which is never triggered as long as Steam is running, but works immediately after Steam is terminated. |
|
Confirming this issue on Fedora 28 with Steam version 1536436120. Steam prevents DPMS from turning off my monitors but does not prevent xautolock from locking my screen. I have no controllers connected and I've disabled in-home streaming. If I close Steam DPMS works and my monitors shut off when expected. If you're trying to reproduce it I've found that if I start Steam but don't interact with it my DPMS settings work as expected, at least with the DPMS timeouts set very low for testing. It's only when I interact with Steam - changing tabs to and from my library, chatting, opening the options menus - that Steam starts interfering with DPMS. It's also possible that letting enough time pass without interacting it will also trigger the bug; I did not test enough to rule this out. |
|
FWIW, I've been experiencing this issue since way before the July update, and I remember noticing it even on Windows more than a year ago. |
|
I've been having this issue since at least before issue #5532 opened. I've got neither org.gnome.ScreenSaver or org.freedesktop.ScreenSaver dbus services and my x11 idle timer continues to increase. Still, my monitors never sleep with steam open (I can just open steam for this issue to take effect, i don't need to interact with it or start a game). How is steam disrupting dpms behavior as it seems x11 idle isn't used and the dbus methods return errors on my system? for ref. sdl2 functions:
|
|
I confirm this exact same issue on my system:
|
|
I'm still experiencing this problem, too. |
|
This is still a problem. Steam is intentionally inhibiting DPMS. Run $ dbus-monitor --session
[...]
method call time=1549222988.474789 sender=:1.315 -> destination=org.freedesktop.ScreenSaver serial=2 path=/org/freedesktop/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=Inhibit
string "My SDL application"
string "Playing a game"
method call time=1549222988.475227 sender=:1.213 -> destination=org.gnome.SessionManager serial=704 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=Inhibit
string "My SDL application"
uint32 0
string "Playing a game"
uint32 8I'm using the Steam client beta, Steam package version 1549129917 (built 2nd Feb 2019 17:21:48). |
|
Any news on this? |
|
Can confirm that this is happening on my Arch install with bspwm as my window manager. |
|
Can confirm also on |
|
I can confirm too. |
|
Also seeing this here. With the Steam client running, no blanking. Without, blanking occurs as it should. I'm using the screen blanker built into X, Devuan beowulf, current Steam beta, Xfce, xf86-video-amdgpu 19.0.1. |
|
Just posting my info from issue #6337 into this thread so people don't have to click though. Also, whether or not I've recently played a game, or played a game since exiting and restarting the Steam client has no bearing on this, it just randomly occurs. Your system information Please describe your issue in as much detail as possible: Steam client randomly disables power management with the notification "My SDL application is currently suppressing power management: playing a game" dosplayed in the Battery and Brightness widget. Exiting Steam and restarting will clear the problem for a random period of time, after which the power management is disabled again with the same notification. Seems to be similar to issue #5532 from about a year ago, but I don't recall having that problem back then. This started happening a few weeks ago, and I've just now taken the time to trace it to the Steam Client. |
|
happens here too, and its quite annoying |
|
I also have this problem, and have for at least several months. Maybe more; I'm not sure when it started. Monitor never turns off when Steam is running, turns off as normal when idle if Steam is not running. |
|
the really weird part is i dont have a org.freedesktop.ScreenSaver nor org.kde.Solid.PowerManagement.PolicyAgent because i run a standalone WM. and i even tried setting the sdl env vars, and it still "inhibits" it. |
|
OS: Fedora 30 I have an applet (Presentation Applet) that tells when apps are inhibiting the screen saver. Frequently, "My SDL application" will inhibit the screensaver, the only way to get rid of it is to log out or close Steam. Ironically, I also have the opposite problem where Steam wont inhibit the screensaver during a game, and the X server doesn't detect my gamepad as input prolonging the sleep timeout, so in gamepad games the screen will turn after 10 minutes of playing unless I use said applet to disable power saving features temporarily. |
|
I have the same issue: I'm using the screensaver built in to X too. |
|
I'm having the same issue. I initially noticed this due to messages like these appearing in KSyslog: Xset confirms DPMS is disabled while Steam is running. While Steam is closed: |
|
This is exacerbated by #6503 due to repeated unblanking. Previously, once forced, the display would remain blanked (except in specific circumstances). |
|
I use a hotkey combo running the command |
|
To add to @tripkin 's comment- |
|
I'm also having this problem, currently with Debian Buster, but it's been an issue for years. I always assumed that, since Steam makes heavy use of browser functionality, and I noticed the problem in Chromium around the same time as Steam, that it's related to this bug with Chromium inhibiting power management: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622 |
|
I have this issue,had to use steam-screensaver-fix from AUR. Can someone setup an donation page for valve so they can hire an dev to fix basic 6 years old bug? |
|
Just open source the code and it'll be fixed in a few days. |
|
Adding to this, I am running Debian (12) Bookworm |
|
screen goes blank for 2 seconds then comes back on.. |
|
For any newcomers to this issue thread, please can we 👍 the original post right at the top if this issue is also occurring for you, and subscribing to the issue, instead of making a "me too" comment and spamming everyone? We know it's still an issue. The issue is Open. 🙏 |
|
Some people are going to want to inhibit the screensaver/dpms some are not. With the steamdeck you can set a monitor poweroff right in the client. If this was enabled in the steam client on linux I suspect most people would be happy. (Except the people that have a special screensaver they want to run). But seems a good place to spend steam-points (like startup movies, etc) |
|
For me (Xubuntu 22.04.5 LTS) the screen actually never turns off again after starting steam once - even if steam and all it's processes were stopped! Only rebooting helps. |
|
The latest beta client supports a "-disable-screensaver-inhibit" command line option that will prevent Steam from inhibiting the screen saver when it detects computer activity. This feature of the Steam client is required on Steam Deck and SteamOS, but depending on your use case on Desktop we realize you may not want this. The Steam client inhibits the screen saver under various conditions such as mouse or controller activity, game streaming, game overlay activity and more. If the system is left idle for roughly 30 seconds and nothing is happening indicating activity on the system, the Steam client will allow the screen saver again. We have not been able to reproduce situations where the Steam client is permanently preventing the screen saver to activate as described above. But if you run into such a problem, you may want to use these two new command line options: "-verbose-screensaver-inhibit" and "-verbose-computer-activity" to understand why the Steam client thinks there is activity on your system. If you still believe there is an issue with the Steam client after that please open a separate issue and provide logs. We've noted reports that explicitly disabling the monitor with "xset dpms force off" may result in the monitor coming back up again after a few seconds. We believe this happens when the command is issued while the Steam client is actively inhibitingthe screen saver. Issuing this command once the Steam client no longer inhibits appears to work as intended. |
|
After testing It's really weird that Steam is inhibiting the screensaver for as long as 30 seconds after it detects activity even if that activity has nothing to do with Steam. That's very bizarre behaviour for any application, and it's obviously going to interfere with any screen locking hotkeys triggered by users. It could make sense if there was a game running, but not if I'm, say, scrolling in my web browser and Steam is in another virtual desktop. |
|
It inhibits it forever and is very easy to reproduce, even with all usb devices unplugged. The AUR package should really cover what if anything needed to be 'known' to reproduce, or just ask someone in the past 6 years here to take 5 mins to do it.. @awused yea especially if steam is minimized + no software running from it, the thing should be entirely inactive. |
|
Everything seems to be working fine for me now. I was using the AUR packages before, but I no longer need them. I agree with the checkbox option. |
|
I've filed #11315 because I think the intended behaviour described in #5607 (comment) is bad enough that it should be fixed, but to keep it separate from the greater issue described in this bug (permanent inhibition without user activity). For what it's worth my monitors did shut off as expected after two hours of inactivity with |
|
|
Running Steam beta client with -verbose-screensaver-inhibit -verbose-computer-activity gave me these messages in the console_log.txt in ~/.local/share/Steam/logsI noticed the "computer activity: mouse" popping up and tried removing my mouse and completely launch everything with the keyboard and notice Steam no longer inhibit screensaver, but the moment I plug in and move my mouse then my monitor will just refused to blank. I use qtile as my WM, I'm not sure if mouse hover focus was affecting it so I turned it off and did another run.It didn't change anything, but I let it ran for a little longer and got something new So far as long as I don't move my mouse the inhibit will not trigger. Also, removing my mouse and running steam will still result in the log showing "computer activity: mouse" and a bunch of "screen saver inhibit". The only difference is the screen will still blank unless I move the mouse. Sorry I'm not a full time developer, and don't usually post bug report, but this has been bugging me out and just trying to share what I found in case it will help |
|
I have done further testing and this is what I found out. I even found a potential fix(?) Everything ran with -verbose-screensaver-inhibit -verbose-computer-activity enabled. At every launch I will get "computer activity: mouse" in console log regardless if the mouse is plugged in. The console will start printing "screen saver inhibit: computer is active" immediately and stopped after approximately a minute. The log will then print "screen saver inhibit: allow". Assume that you still do not plug in your mouse and start operating your PC through the keyboard, the console will remain silent and DPMS will not be affected. This is weird because I was assuming that operating the keyboard will trigger another inhibit. But I think Steam does not work well with purely just DPMS. If I plug in a mouse and start moving and immediately unplug it, Steam will print "Screen saver inhibit: inhibit" and start spamming "screen saver inhibit: computer is active" for another one minute. Then this time DPMS will no longer work. So I assume the first inhibit triggered by the mouse activity in console did not affect DPMS for some reason. Cause DPMS will still work regardless of if Steam is printing "screen saver inhibit: computer is active". But if the console print "screen saver inhibit: inhibit", DPMS will stop working. So the fix: I don't know if this will work the same on the full release, but everything was tested on the beta version. I might do some test on the full release later and post another comment. |
|
Did another test, using XScreensaver bypass Steam inhibit for some reason, so if you are gaming with controller your monitor will blank mid game, it will still blank even if I use Big Picture. I gave up and just stole a bash script online (checkout lightsonplus by devkral) and use it to detect if a game is in full screen mode and disable screensaver. |
|
@DreamsOneiro wrote:
Steam does consider the mouse moving as computer activity, and will prevent the screensaver for a period of time based on that. That seems pretty normal. It would be an issue if just having your mouse plugged in, without using it would permanently prevent the screensaver, but that's not what's happening here is it? Steam has no notion of 'DPMS vs screensaver', it just uses the dbus APIs to inhibit or allow the screensaver. If DPMS ends up being permanently disabled despite Steam issuing the allow again, that doesn't sound like a problem with steam anymore. |
It's not normal for an individual application to do that when they're not the subject of the mouse activity. Especially not also silently inhibiting it for a lengthy period of time after. I have no other applications that do either of those, Steam on Linux is extremely abnormal. Most applications don't ever need to inhibit the screen saver based on mouse or keyboard activity anyway. Screen saver inhibition is usually used in the opposite case, when there's no user input but something else is preventing it, like video playback. A desktop environment or window manager (or something in a similar vein like xautolock) are about the only cases where it makes sense to track global inputs, because they're the ones also managing the screen saver. Maybe on Steam OS or Steam Deck, Steam fits that description, but it doesn't on regular desktop clients which is what this bug is about. |
No its not for several reasons:
|
my setup is not using the dbus service, it is using the XSS method of
ok, now i have added logging into xserver/Xext. i can see that both with dbus service that starts with suspend_cookie = 0 and if there is no dbus service, a persistent inhibit is added to X. |
|
Keeping the monitor awake from mouse movements is definitely not steams responsibility lol When a game is running, it should just inhibit screen saver, the same way when a video is playing full screen it is inhibited. That's really all that anyone needs and keeps it fairly simple. Steam can also inhibit for controller movement in big picture mode, as OSes usually won't inhibit for controller movement so that one can be steams responsibility. |
and others
Your system information
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Laptop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD FX(tm)-8350 Eight-Core Processor
CPU Family: 0x15
CPU Model: 0x2
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4000 Mhz
8 logical processors
8 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"NAME=Gentoo" (64 bit)
Kernel Name: Linux
Kernel Version: 4.17.10
X Server Vendor: The X.Org Foundation
X Server Release: 11905000
X Window Manager: Metacity (Marco)
Steam Runtime Version: steam-runtime-beta-release_2018-06-14
Video Card:
Driver: NVIDIA Corporation GeForce GTX 1050 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 396.45
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x10de
DeviceID: 0x1c82
Revision Not Detected
Number of Monitors: 1
Number of Video Cards Not Detected
Primary Display Resolution: 1920 x 1200
Desktop Resolution: 1920 x 1200
Primary Display Size: 20.39" x 12.76" (24.02" diag)
51.8cm x 32.4cm (61.0cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 4096 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Realtek ALC892
Memory:
RAM: 15918 Mb
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 468427 Mb
Largest Free Hard Disk Block: 20083 Mb
VR Headset: None detected
Recent Failure Reports:
Please describe your issue in as much detail as possible:
Since the update to the version with the new chat features, the monitor no longer shuts off when idle. The screensaver will blank, but the monitor remains on. DPMS is enabled. If I exit steam, the monitor shuts off again when idle.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: