[GH-ISSUE #436] Barrier prevents screens from going to sleep #339

Open
opened 2026-05-05 06:03:51 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @mirh on GitHub (Sep 14, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/436

Operating Systems

Server: Windows 7

Client: Manjaro Linux

Barrier Version

2.31 git/snapshot

Steps to reproduce bug

  1. Connect the two computers
  2. Don't touch them for the amount of time that it should take for the monitors to turn off
  3. They always keep on
Originally created by @mirh on GitHub (Sep 14, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/436 ### Operating Systems ### Server: Windows 7 Client: Manjaro Linux ### Barrier Version ### 2.31 git/snapshot ### Steps to reproduce bug ### 1. Connect the two computers 2. Don't touch them for the amount of time that it should take for the monitors to turn off 3. They always keep on
gitea-mirror added the
windows
linux
labels 2026-05-05 06:03:51 -06:00
Author
Owner

@cowbe0x004 commented on GitHub (Sep 18, 2019):

Check out this thread
https://members.symless.com/forums/topic/4794-does-synergy-prevent-monitor-from-going-to-sleep/

<!-- gh-comment-id:532480975 --> @cowbe0x004 commented on GitHub (Sep 18, 2019): Check out this thread https://members.symless.com/forums/topic/4794-does-synergy-prevent-monitor-from-going-to-sleep/
Author
Owner

@mirh commented on GitHub (Sep 18, 2019):

I'm sure that'll work
But still, I don't understand whatever rationale was behind this code to begin with.
And why nobody still didn't fix it.

<!-- gh-comment-id:532738322 --> @mirh commented on GitHub (Sep 18, 2019): I'm sure that'll work But still, I don't understand whatever rationale was behind [this](https://github.com/debauchee/barrier/blob/v2.3.1/src/lib/platform/XWindowsScreen.cpp#L266) [code]( https://github.com/debauchee/barrier/blob/v2.3.1/src/lib/platform/MSWindowsScreen.cpp#L1450) to begin with. And why nobody still didn't fix it.
Author
Owner

@mirh commented on GitHub (Sep 19, 2019):

Ok, after sleeping on it, I guess like it may even have its sense to have this kind of feature
(assuming "virtual" inputs aren't treated the same of physical ones power-management-wise... which actually seemed to be the case after reading some code, but I could easily be wrong)
You wouldn't like your client to go to sleep while you are remote-ing in it.

Why the hell is the same thing also being enforced on the host though? And would it have taken too much time to add an activity/screen check?

<!-- gh-comment-id:533251468 --> @mirh commented on GitHub (Sep 19, 2019): Ok, after sleeping on it, I guess like it may even have its sense to have this kind of feature (assuming "virtual" inputs aren't treated the same of physical ones power-management-wise... which actually seemed to be the case after reading some code, but I could easily be wrong) You wouldn't like your client to go to sleep while you are remote-ing in it. Why the hell is the same thing also being enforced on the host though? And would it have taken too much time to add an activity/screen check?
Author
Owner

@remotejob commented on GitHub (Oct 15, 2019):

The same problem
in my case:

Operating Systems
Server: Ubuntu 18.04
Client: Ubuntu 18.04

Barrier Version
commit 14a708db33

But only Client ON not to go to sleep.

<!-- gh-comment-id:542019479 --> @remotejob commented on GitHub (Oct 15, 2019): The same problem in my case: Operating Systems Server: Ubuntu 18.04 Client: Ubuntu 18.04 Barrier Version commit 14a708db336fbe4e9d66fa835cf2b0ae8dd453dd But only Client ON not to go to sleep.
Author
Owner

@OptimusGREEN commented on GitHub (May 21, 2023):

yeah im currently struggling with this on an ubuntu 22.04 client. It would be great if there was a solution soon.

<!-- gh-comment-id:1556290008 --> @OptimusGREEN commented on GitHub (May 21, 2023): yeah im currently struggling with this on an ubuntu 22.04 client. It would be great if there was a solution soon.
Author
Owner

@andreysm commented on GitHub (Sep 13, 2024):

Encountered this on Windows.
Disabling "Synchronize screen savers" checkbox at "Advanced server settings" tab solved the problem.
The system doesn't go to sleep, but the screen does. (powercfg /requests is informative.)

<!-- gh-comment-id:2350093141 --> @andreysm commented on GitHub (Sep 13, 2024): Encountered this on Windows. Disabling "Synchronize screen savers" checkbox at "Advanced server settings" tab solved the problem. The system doesn't go to sleep, but the screen does. (`powercfg /requests` is informative.)
Author
Owner

@vathanac commented on GitHub (Nov 18, 2024):

Encountered this on Windows. Disabling "Synchronize screen savers" checkbox at "Advanced server settings" tab solved the problem. The system doesn't go to sleep, but the screen does. (powercfg /requests is informative.)

I can't find where to disable "Synchronize screen savers". Can you elaborate?

<!-- gh-comment-id:2484154381 --> @vathanac commented on GitHub (Nov 18, 2024): > Encountered this on Windows. Disabling "Synchronize screen savers" checkbox at "Advanced server settings" tab solved the problem. The system doesn't go to sleep, but the screen does. (`powercfg /requests` is informative.) I can't find where to disable "Synchronize screen savers". Can you elaborate?
Author
Owner

@andreysm commented on GitHub (Nov 19, 2024):

barrier-settings

<!-- gh-comment-id:2485020643 --> @andreysm commented on GitHub (Nov 19, 2024): ![barrier-settings](https://github.com/user-attachments/assets/b413b06e-2355-484c-a314-a5861ced3a73)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#339
No description provided.