Bug 357288 - Setting "Screen Energy Saving" in "Energy Saving" config has no effect
Summary: Setting "Screen Energy Saving" in "Energy Saving" config has no effect
Status: RESOLVED FIXED
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.9.4
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-29 00:12 UTC by Raman Gupta
Modified: 2023-04-25 12:13 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Configuration for power management (697 bytes, text/plain)
2015-12-29 00:13 UTC, Raman Gupta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raman Gupta 2015-12-29 00:12:42 UTC
Setting the "Screen Energy Saving" value to switch off monitors (under "On AC Power") in "Energy Saving" config has no effect. The monitors do not turn off, and "xset q" shows:

DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

Using "xset dpms force off" works fine, as does "xset dpms 600 600 600". After running that command the monitors correctly go to power saving mode.

However, as soon as any changes are made in the KDE configuration, the dpms settings go back to 0/0/0.

Reproducible: Always
Comment 1 Raman Gupta 2015-12-29 00:13:42 UTC
Created attachment 96345 [details]
Configuration for power management
Comment 2 Jake Cobb 2016-04-13 14:51:12 UTC
I have this same problem running KDE 5.15.0 (on Ubuntu 15.10) on iMac hardware.  If I disable screen locking (under System Settings > Desktop Behavior > Screen Locking), then the monitor will power off as expected with my Screen Energy Saving setting.  Just having screen locking enabled seems to prevent the power off from working, e.g. if I tell it to switch off after 1 min and screen locking is set after 5 minutes, nothing will happen after 1 minute, so it doesn't seem to be the screen locker re-enabling the monitor.
Comment 3 Jake Cobb 2016-04-13 19:38:47 UTC
For some further information, allowing the screen to lock from the power management settings will wake it back up when the screen locks.

Specifically, Desktop Behavior > Screen Locking is off.  Power Management > Energy Saving has:
-Screen Energy Saving checked, Switch off after 1 min.
-Suspend session checked, After 2 min Lock screen.

Then the monitor sleeps after one minute but turns back on with the lock screen after the second minute.
Comment 4 Raman Gupta 2016-08-07 18:52:21 UTC
This seemed to have been working for a while, but is now broken again in 5.7.3.
Comment 5 Raman Gupta 2016-09-01 14:17:09 UTC
(In reply to Jake Cobb from comment #2)
> I have this same problem running KDE 5.15.0 (on Ubuntu 15.10) on iMac
> hardware.  If I disable screen locking (under System Settings > Desktop
> Behavior > Screen Locking), then the monitor will power off as expected with
> my Screen Energy Saving setting.

Seems to be a different issue. I don't have screen locking enabled, and my monitors still do not power off.
Comment 6 Raman Gupta 2016-09-12 17:31:30 UTC
At some point in the near past, this started working again -- plasma 5.7.3, KDE frameworks 5.25.0, QT 5.6.1, Kernel 4.7.2. For now, I'm going to close it as Fixed, Uptream.
Comment 7 Raman Gupta 2016-09-26 23:23:59 UTC
Well, this problem is back again, for no apparent reason. Simply applied some updates (kernel 4.7.3) and rebooted, and now monitor power-save / sleep again does not work.
Comment 8 Jiri Tyr 2016-11-10 15:02:02 UTC
I'm suffering from the same issue. The screen power management doesn't work properly when the screen is locked. This is the log from xset -q:

$ while [ true ]; do echo -n '['$(date +%T)']'; xset -q | grep -A2 Standby | xargs -I'{}' echo -n ' {};' | sed -r 's/\s+/ /g'; echo -e "\r"; sleep 1; done
# I locked the screen
[13:02:15] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is On;
...
[13:22:39] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is On;
[13:22:40] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is in Standby;
...
[14:41:52] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is in Standby;
# Here I unlocked the screen
[14:41:53] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is On;
...
[14:42:02] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is On;
# Flickering between the DPMS is Enabled/Disabled occurs even if the screen is unlocked
[14:42:03] Standby: 0 Suspend: 0 Off: 0; DPMS is Disabled;
...
[14:42:14] Standby: 0 Suspend: 0 Off: 0; DPMS is Disabled;
[14:42:15] Standby: 120 Suspend: 180 Off: 240; DPMS is Enabled; Monitor is On;
...

It would be really great if this could be fixed.
Comment 9 Raman Gupta 2016-12-01 13:57:30 UTC
Still the same issue on Plasma 5.8.4, QT 5.6.2 (Fedora 24).
Comment 10 Raman Gupta 2017-05-09 14:06:51 UTC
Now on Plasma 5.9.4, I can see in the battery manager applet that Power Management is suppressed by a tab in google-chrome-stable. The tab doesn't exist, and Chrome isn't even running (confirmed with ps as root), but hey, at least now there is some information that explains why the energy saving isn't working.
Comment 11 Yevgeny Kosarzhevsky 2018-09-18 09:58:35 UTC
I have similar issue in 5.49.0. I switch off all screen power saving but it goes off anyway and xset q shows the following:
$ xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    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:  200    repeat rate:  40
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  20/10    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
Colors:
  default colormap:  0x22    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins
DPMS (Energy Star):
  Standby: 300    Suspend: 330    Off: 360
  DPMS is Enabled
  Monitor is On
Comment 12 Andrew 2019-07-14 16:54:35 UTC
Disappointed to see this problem is still around after so long.  I had worked around this by modifying my xorg.conf to disable DPMS, but some recent update broke this again.  After about 15 minutes, my monitors will blank, shut off, or whatever it is that's happening, sometimes in the middle of games if it's not looking at controller input to see if I'm actively using the computer.  DPMS is still disabled from the last time I tweaked this setting, and it's not working anymore; even still, KDE should be able to set this itself as per the system settings anyway.  Current software versions are:

Kubuntu 18.04 64-bit
Plasma 5.12.7
Frameworks 5.44.0
Qt 5.9.5
Kernel 4.18.16-041816-generic
Comment 13 al F 2021-11-16 13:46:00 UTC
Same problem here, running plasma-desktop as part of Kubuntu (was Plasma 5.18.5)  and on top of Linux Mint 20.2 with KDE Plasma Version: 5.18.7. KDE Frameworks Version: 5.68.0, Qt Version: 5.12.8, Kernel Version: 5.4.0-90-generic.

Regardless of settings made in "System settings > Energy Saving" and regardless of being on AC or battery, screen is dimmed or turned off at intervals that seem to be set elsewhere. I filed this as a bug at https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1942876

Output of `xset q`:

DPMS (Energy Star):
  Standby: 300    Suspend: 450    Off: 600
  DPMS is Enabled
  Monitor is On

These numbers does not correspond to any of my settings
Comment 14 Al 2022-01-02 21:43:55 UTC
I am having similar issues here with the power saving not keeping the screen blanked. I can set it to blank the screen (in 1 minute for example), and it will blank all 3 monitors. They will go blank, even go into their power save mode for a second, but then everything comes right back on again. It does the same if I set a shortcut to blank the screen - goes off but then back on again in about 10 seconds or so. I am using an AMD X3900 X570 system, Radeon RX 5500XT video, 3 monitors (one of them is a different size than the other 2 FWIW) similar to a related report listed under bug 440350. Currently running the latest version of Fedora 35 KDE Plasma 5.23.4 Framework 5.89.0 kernel 5.15.12-200 and using X11 (Wayland does not work well here - maybe that is a clue).
Comment 15 Al 2022-01-06 20:17:43 UTC
I just tried a new install of KDE Neon (an Ubuntu base rather than a Fedora base), set the power saver for 1 minute, and the screen went blank for about 10 seconds, then came right back on again, Same as the Fedora 35 base.
Comment 16 Raman Gupta 2022-01-06 21:24:29 UTC
As the OP I don't have this issue on recent KDE versions, so I'll go ahead and close.
Comment 17 skierpage 2023-02-21 21:16:37 UTC
(In reply to Al from comment #14)
> I am having similar issues here with the power saving not keeping the screen
> blanked. I can set it to blank the screen (in 1 minute for example), and it
> will blank all 3 monitors. They will go blank, even go into their power save
> mode for a second, but then everything comes right back on again.

It could be some USB device. If so it would probably interfere with switched off screens and the lock screen. There's some guidance in "PC wakes up from suspend due to USB events".
Comment 18 mjay 2023-04-25 12:00:17 UTC
(In reply to Al from comment #14)
> I am having similar issues here with the power saving not keeping the screen
> blanked. I can set it to blank the screen (in 1 minute for example), and it
> will blank all 3 monitors. They will go blank, even go into their power save
> mode for a second, but then everything comes right back on again. It does
> the same if I set a shortcut to blank the screen - goes off but then back on
> again in about 10 seconds or so. I am using an AMD X3900 X570 system, Radeon
> RX 5500XT video, 3 monitors (one of them is a different size than the other
> 2 FWIW) similar to a related report listed under bug 440350. Currently
> running the latest version of Fedora 35 KDE Plasma 5.23.4 Framework 5.89.0
> kernel 5.15.12-200 and using X11 (Wayland does not work well here - maybe
> that is a clue).

This sounds like a similar problem i had with Kscreen2. Kscreen2 would, note that a 
displayport connected monitor was powered down, then kscreen2, then moved the windows
 off that monitor and onto other monitors, tripping a event, powering them back on again.
Comment 19 mjay 2023-04-25 12:13:13 UTC
(In reply to mjay from comment #18)
> (In reply to Al from comment #14)
> > I am having similar issues here with the power saving not keeping the screen
> > blanked. I can set it to blank the screen (in 1 minute for example), and it
> > will blank all 3 monitors. They will go blank, even go into their power save
> > mode for a second, but then everything comes right back on again. It does
> > the same if I set a shortcut to blank the screen - goes off but then back on
> > again in about 10 seconds or so. I am using an AMD X3900 X570 system, Radeon
> > RX 5500XT video, 3 monitors (one of them is a different size than the other
> > 2 FWIW) similar to a related report listed under bug 440350. Currently
> > running the latest version of Fedora 35 KDE Plasma 5.23.4 Framework 5.89.0
> > kernel 5.15.12-200 and using X11 (Wayland does not work well here - maybe
> > that is a clue).
> 
> This sounds like a similar problem i had with Kscreen2. Kscreen2 would, note
> that a 
> displayport connected monitor was powered down, then kscreen2, then moved
> the windows
>  off that monitor and onto other monitors, tripping a event, powering them
> back on again.

EDIT: My problem, was not xscreen2, but rather my monitors in a hdmi/dp setup, with its input source detection, that was the culprit. not xscreen2, see https://gitlab.freedesktop.org/drm/amd/-/issues/1719