Screen saver no longer kicks in on client (i.e., the screen remains on forever)

This issue has been migrated from old Barrier Github repository https://github.com/debauchee/barrier/issues/843

Issue created on: 2020-08-18 by @sandrosilvestre Issue last updated on: 2020-10-21

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"

Commented on: 2020-08-26 by @wriver4

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.

Commented on: 2020-08-27 by @sandrosilvestre

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.

Commented on: 2020-08-29 by @huizichin

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

Commented on: 2020-10-19 by @CStrauch

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.

Commented on: 2020-10-20 by @sandrosilvestre

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

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.

Commented on: 2020-10-21 by @CStrauch

@sandrosilvestre, thanks!

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

Thanks a lot for your help!

input-leap / input-leap