Power management on Linux client is inhibited

fagg commented 5 years ago

Operating Systems

Server: Arch Linux

Client: Arch Linux

Barrier Version

2.1.0 RELEASE

Steps to reproduce bug

Power management on server works fine (screen goes to sleep when inactive). On the client, however, the screen does not turn off while Barrier is running.

Power settings (with Barrier running):

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:  660    repeat rate:  25
  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:  600
Colors:
  default colormap:  0x22    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/misc,/usr/share/fonts/TTF,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Disabled

Without Barrier running:

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:  660    repeat rate:  25
  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:  600    cycle:  600
Colors:
  default colormap:  0x22    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/misc,/usr/share/fonts/TTF,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On

If it helps, the client is a laptop (Thinkpad X270), server is a desktop. Closing the lid on the laptop with Barrier running still makes it go to sleep (ala systemctl suspend).

I'd expect that the screen power settings on the client obey the local settings, and be woken up when there is input from the server's keyboard/mouse.

Other info

When did the problem start to occur? Has always happened
Is there a way to work around it? Can't find one
Does this bug prevent you from using Barrier entirely? No

a7hybnj2 commented 5 years ago

I am experiencing this same issue. Windows 8.1 as server and Arch Linux as client.

edalongeville commented 5 years ago

Me too with a windows 10 server and an Ubuntu 18.04 client.

patrickli commented 5 years ago

Same problem. MacOS server and Windows 10 client.

patrickli commented 5 years ago

Some details.

C:\WINDOWS\system32>powercfg -requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume9\Program Files\Barrier\barrierc.exe

SYSTEM:
[PROCESS] \Device\HarddiskVolume9\Program Files\Barrier\barrierc.exe

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

noisyshape commented 5 years ago

The server has an option called 'Synchronize screen savers'. Does this happen with that option disabled?

patrickli commented 5 years ago

The server has an option called 'Synchronize screen savers'. Does this happen with that option disabled?

I tried that and it removed the DISPLAY requests. The SYSTEM still exists. I tried to disable drag and drop and clipboard sharing but these doesn't make any difference.

xorander00 commented 5 years ago

Same here. I disabled the "Synchronize screen savers" option & restarted Barrier on both the server & client. Upon launch, it disabled DPMS again. However, after after re-enabling DPMS, the setting seems to be sticking this time around.

zeorin commented 4 years ago

Still an issue for me. Linux server and client.

zeorin commented 4 years ago

Scratch that, I didn't realize that "Synchronize screen savers" was ticked by default. When I unticked it, the client now has DPMS enabled when barrier is running.

moseschanx commented 2 years ago

My solution for this on windows is : powercfg -requestsoverride process barrierc.exe system display on Linux ( manually set timeout for screen saver ) : xset +dpms s <yourtimeout> <cycles> though DPMS will still be triggered off when barrier interacts with your desktop, this will make your monitor auto blank again.

debauchee / barrier