github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 22:01:23 -06:00

[GH-ISSUE #843] Screen saver no longer kicks in on client (i.e., the screen remains on forever) #672

New issue

Open

opened 2026-05-05 06:52:40 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 06:52:40 -06:00

Owner

Originally created by @sandrosilvestre on GitHub (Aug 18, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/843

Operating Systems

Server: Windows 10 Pro v1909 build 18363.959 / Linux Mint x86_64 Xfce 19.2 (Tina). Dual-boot system where both OS are set as Barrier server.

Client: Linux Mint x86_32 Xfce (Tina)

Barrier Version

Windows: 2.3.3-release-3395cca9 build date: 14 July 2020 (downloaded as pre-compiled .exe)

Linux: 2.2.2-release protocol 1.6 (server and client installed via SnapCraft)

(All should be the latest version as of today, 2020-08-18)

Steps to reproduce bug

I have noticed that the screen saver (Light Locker) on client no longer kicks in i.e., the screen remains on forever. So, in order to reproduce the problem you have just to set up your screen saver on client and wait.

(I understand it might be a total nonsense for some people to have a screen saver on a KVM-managed system so this may not be a bug at all but just a low-priority enhancement.)

Update on 2020-10-20: After 2 months leaving with this problem I have to say that it is indeed annoying!

Other info

Light Locker settings on client are managed by Xfce Power Manager

The client hardware is a Sony Vaio notebook from Windows XP era (circa 2005, now a Mint-only machine). So the following lines at /etc/default/grub might be important:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Windows acpi_backlight=video"
GRUB_CMDLINE_LINUX=""

Driver: nouveau.

The user, USERNAME, is a sudoer.

Client is set to be autostarted on login:
env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/barrier_barrier.desktop /snap/bin/barrier.barrierc --debug ERROR --log /home/USERNAME/Logs/snap-barrier-barrierc.log --restart --daemon --name CLIENTNAME --enable-drag-drop --enable-crypto [SERVERNAME]:24800
Note: running this same line at terminal reports nothing unusual.

/home/USERNAME/Logs/snap-barrier-barrierc.log reports nothing usual (please keep in mind that I am setting up Barrier and doing some tests so these messages should be considered normal)
connected to server
[2020-08-17T18:10:47] FATAL: X display has unexpectedly disconnected
connected to server
[2020-08-17T18:14:57] FATAL: X display has unexpectedly disconnected
connected to server
[2020-08-18T09:27:52] ERROR: failed to connect to server: server is not responding
connected to server
[2020-08-18T10:34:29] WARNING: failed to connect to server: Timed out
connected to server
connected to server

On System Log I have found these lines:
SECCOMP code=0x50000
AVC apparmor="DENIED"
USER_AVC apparmor="DENIED"

Originally created by @sandrosilvestre on GitHub (Aug 18, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/843 ### Operating Systems ### Server: Windows 10 Pro v1909 build 18363.959 / Linux Mint x86_64 Xfce 19.2 (Tina). Dual-boot system where both OS are set as Barrier server. Client: Linux Mint x86_32 Xfce (Tina) ### Barrier Version ### Windows: 2.3.3-release-3395cca9 build date: 14 July 2020 (downloaded as pre-compiled .exe) Linux: 2.2.2-release protocol 1.6 (server and client installed via SnapCraft) (All should be the latest version as of today, 2020-08-18) ### Steps to reproduce bug ### I have noticed that the screen saver (Light Locker) on client no longer kicks in i.e., the screen remains on forever. So, in order to reproduce the problem you have just to set up your screen saver on client and wait. (I understand it might be a total nonsense for some people to have a screen saver on a KVM-managed system so this may not be a bug at all but just a low-priority enhancement.) _Update on 2020-10-20: After 2 months leaving with this problem I have to say that it is indeed annoying!_ ### Other info ### Light Locker settings on client are managed by Xfce Power Manager The client hardware is a Sony Vaio notebook from Windows XP era (circa 2005, now a Mint-only machine). So the following lines at **/etc/default/grub** might be important: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash **acpi_osi=Windows acpi_backlight=video**" GRUB_CMDLINE_LINUX="" Driver: **nouveau**. The **user**, **USERNAME**, is a **sudoer**. **Client** is set to be **autostarted** on **login**: **env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/barrier_barrier.desktop /snap/bin/barrier.barrierc --debug ERROR --log /home/USERNAME/Logs/snap-barrier-barrierc.log --restart --daemon --name CLIENTNAME --enable-drag-drop --enable-crypto [SERVERNAME]:24800** Note: running this same line at terminal reports nothing unusual. **/home/USERNAME/Logs/snap-barrier-barrierc.log** reports nothing usual (please keep in mind that I am setting up Barrier and doing some tests so these messages should be considered normal) **connected to server [2020-08-17T18:10:47] FATAL: X display has unexpectedly disconnected connected to server [2020-08-17T18:14:57] FATAL: X display has unexpectedly disconnected connected to server [2020-08-18T09:27:52] ERROR: failed to connect to server: server is not responding connected to server [2020-08-18T10:34:29] WARNING: failed to connect to server: Timed out connected to server connected to server** On **System Log** I have found these lines: **SECCOMP code=0x50000 AVC apparmor="DENIED" USER_AVC apparmor="DENIED"**

gitea-mirror commented

2026-05-05 06:52:45 -06:00

Author

Owner

@wriver4 commented on GitHub (Aug 26, 2020):

I had a similar problem. I discovered if the cursor is not left on the server the screensavers do not work as expected. I at least get a notification that it is prevented from executing.

@wriver4 commented on GitHub (Aug 26, 2020): I had a similar problem. I discovered if the cursor is not left on the server the screensavers do not work as expected. I at least get a notification that it is prevented from executing.

gitea-mirror commented

2026-05-05 06:52:46 -06:00

Author

Owner

@sandrosilvestre commented on GitHub (Aug 27, 2020):

Hi @wriver4,

I do not get any notification about what is preventing it from executing - not even on system log. Perhaps it is related to the way I am running Barrier - as a daemon in my session.

@sandrosilvestre commented on GitHub (Aug 27, 2020): Hi @wriver4, I do not get any notification about what is preventing it from executing - not even on system log. Perhaps it is related to the way I am running Barrier - as a daemon in my session.

gitea-mirror commented

2026-05-05 06:52:49 -06:00

Author

Owner

@MidnightQuery commented on GitHub (Aug 29, 2020):

i have the same issue synchronised screen saver make it so that the client doesnt turn off the screen at all

@MidnightQuery commented on GitHub (Aug 29, 2020): i have the same issue synchronised screen saver make it so that the client doesnt turn off the screen at all

gitea-mirror commented

2026-05-05 06:52:51 -06:00

Author

Owner

@CStrauch commented on GitHub (Oct 19, 2020):

Hi @sandrosilvestre,

I've noticed the same problem here. I work on a Linux machine and have a laptop running Windows 10 home on my desk, also.
I thought there was a problem with my Windows install when the screen saver was not starting (and the screen would not turn off). After the last Windows Update it was working again and I credited it to the update.
Until I noticed barrier was not running on Windows. After I started it, the screen saver stopped working.
When I stopped the service on the Windows machine, the screen saver worked again.

And I disagree it is a minor thing. In my case it is extremely annoying, due to the fact is a machine very lightly used (a laptop) that does not turn the display off when it's idle. Not even at night.

@CStrauch commented on GitHub (Oct 19, 2020): Hi @sandrosilvestre, I've noticed the same problem here. I work on a Linux machine and have a laptop running Windows 10 home on my desk, also. I thought there was a problem with my Windows install when the screen saver was not starting (and the screen would not turn off). After the last Windows Update it was working again and I credited it to the update. Until I noticed barrier was not running on Windows. After I started it, the screen saver stopped working. When I stopped the service on the Windows machine, the screen saver worked again. And I disagree it is a minor thing. In my case it is extremely annoying, due to the fact is a machine very lightly used (a laptop) that does not turn the display off when it's idle. Not even at night.

gitea-mirror commented

2026-05-05 06:52:53 -06:00

Author

Owner

@sandrosilvestre commented on GitHub (Oct 20, 2020):

Hello @CStrauch,

Thanks for your feedback.

First of all, you are totally right: this bug is extremely annoying. I will do my best to update my initial statement.

If do not mind my asking, I would like you to try the following Options on [Configure Server...] and see if the problem persists:

Another point: I have tried both flathub and snapcraft versions of the tool and it might be nonsense but the snapcraft version seems better to me than the one at flathub. Perhaps you could tell us which package you are using in Linux.

@sandrosilvestre commented on GitHub (Oct 20, 2020): Hello @CStrauch, Thanks for your feedback. First of all, you are totally right: this bug is extremely annoying. I will do my best to update my initial statement. If do not mind my asking, I would like you to try the following Options on **[Configure Server...]** and see if the problem persists: ![Barrier Screenshot 2020-10-20 200921](https://user-images.githubusercontent.com/21298159/96653906-89f6f600-1310-11eb-88d4-0bd99353978d.png) **Another point:** I have tried both flathub and snapcraft versions of the tool and it might be _nonsense_ but the **snapcraft version seems better to me** than the one at flathub. Perhaps you could tell us which package you are using in Linux.

gitea-mirror commented

2026-05-05 06:52:55 -06:00

Author

Owner

@CStrauch commented on GitHub (Oct 21, 2020):

@sandrosilvestre, thanks!

It worked! The screensaver (and the screen off) worked exactly as it should.

Thanks a lot for your help!

@CStrauch commented on GitHub (Oct 21, 2020): @sandrosilvestre, thanks! It worked! The screensaver (and the screen off) worked exactly as it should. Thanks a lot for your help!

gitea-mirror commented

2026-05-05 06:52:57 -06:00

Author

Owner

@thedoh commented on GitHub (Nov 29, 2021):

Windows 11 screensaver will not engage with barriers.exe running.

Workaround:
https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/powercfg-command-line-options#option_requestsoverride

open command prompt with admin rights
powercfg /REQUESTSOVERRIDE process barriers.exe display

@thedoh commented on GitHub (Nov 29, 2021): Windows 11 screensaver will not engage with barriers.exe running. Workaround: https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/powercfg-command-line-options#option_requestsoverride open command prompt with admin rights `powercfg /REQUESTSOVERRIDE process barriers.exe display`

gitea-mirror commented

2026-05-05 06:52:59 -06:00

Author

Owner

@rickgitdone commented on GitHub (Feb 1, 2022):

I run this on 2 Linux Ubuntu 18.04 LTS Desktops 1 as server other as client and the above setting 'Don't take foreground on window on Windows Server' fixed my screen saver issue on both Linux Desktops. This would be a good default item so others don't see this persistent anomaly... both version 2.4.0-release-ac5a1bfd

@rickgitdone commented on GitHub (Feb 1, 2022): I run this on 2 Linux Ubuntu 18.04 LTS Desktops 1 as server other as client and the above setting 'Don't take foreground on window on Windows Server' fixed my screen saver issue on both Linux Desktops. This would be a good default item so others don't see this persistent anomaly... both version 2.4.0-release-ac5a1bfd

gitea-mirror commented

2026-05-05 06:53:00 -06:00

Author

Owner

@poleguy commented on GitHub (Sep 13, 2023):

I have 2 Linux Ubuntu 22.04 desktops as client and server. Setting as shown here in the image doesn't reliably allow the screensaver to work on the client. Barrier 2.4.0-release-00000000 release.

@poleguy commented on GitHub (Sep 13, 2023): I have 2 Linux Ubuntu 22.04 desktops as client and server. Setting as shown here in the image doesn't reliably allow the screensaver to work on the client. Barrier 2.4.0-release-00000000 release.

No labels

Rows
Columns