github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #177] Synchronized Desktop Locking #144

New issue

Open

opened 2026-05-05 05:22:39 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 05:22:39 -06:00

Owner

Originally created by @DragoonAethis on GitHub (Nov 17, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/177

Operating Systems/Barrier Version

Barrier: 2.1.0 (everywhere)
Server: Arch (w/ KDE 5.14)
Client: Windows 10 (1803)

Feature request

Currently there are some keystrokes that are not possible to easily emulate under most platforms. One of these is Win+L which locks the Windows session, others would emulate keystrokes like Ctrl-Alt-L to lock Gnome, KDE sessions (and sometimes, emulated keystrokes aren't caught). This is a known bug for years under Synergy.

A possible solution would be to implement OS-specific desktop locking functions (eg running loginctl lock-session under Linux, calling LockWorkStation on user32.dll under Windows, calling SACLockScreenImmediate from the login framework under macOS), and have these available in a portable manner as an action (so that one could add something like keystroke(ctrl+alt+l) = lockScreen(*) to the config and have all/chosen/current screen locked).

Originally created by @DragoonAethis on GitHub (Nov 17, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/177 ### Operating Systems/Barrier Version ### - Barrier: 2.1.0 (everywhere) - Server: Arch (w/ KDE 5.14) - Client: Windows 10 (1803) ### Feature request ### Currently there are some keystrokes that are not possible to easily emulate under most platforms. One of these is Win+L which locks the Windows session, others would emulate keystrokes like Ctrl-Alt-L to lock Gnome, KDE sessions (and sometimes, emulated keystrokes aren't caught). This is a [known bug for years under Synergy](https://github.com/symless/synergy-core/issues/3084). A possible solution would be to implement OS-specific desktop locking functions (eg running `loginctl lock-session` under Linux, calling `LockWorkStation` on user32.dll under Windows, calling `SACLockScreenImmediate` from the `login` framework under macOS), and have these available in a portable manner as an action (so that one could add something like `keystroke(ctrl+alt+l) = lockScreen(*)` to the config and have all/chosen/current screen locked).

gitea-mirror added the

enhancement

label 2026-05-05 05:22:39 -06:00

gitea-mirror commented

2026-05-05 05:22:45 -06:00

Author

Owner

@a7hybnj2 commented on GitHub (Nov 30, 2018):

would be great to have this working. Even my 'sync screen savers' isn't working. I read it might have to do with not using xscreensaver on my linux server but even trying that did not produce results.

@a7hybnj2 commented on GitHub (Nov 30, 2018): would be great to have this working. Even my 'sync screen savers' isn't working. I read it might have to do with not using xscreensaver on my linux server but even trying that did not produce results.

gitea-mirror commented

2026-05-05 05:22:48 -06:00

Author

Owner

@ghost commented on GitHub (Apr 23, 2020):

This would be a great feature. Currently I'm working with two laptops, a linux client next to a windows server. When I'm working on the windows laptop for too long, and I see my linux screen fading out(lock screen goes in a fading fasion...), then I can prevent it from locking by quickly moving my mouse over to the linux client. Would be great to have a feature that prevents the need for this action!

@ghost commented on GitHub (Apr 23, 2020): This would be a great feature. Currently I'm working with two laptops, a linux client next to a windows server. When I'm working on the windows laptop for too long, and I see my linux screen fading out(lock screen goes in a fading fasion...), then I can prevent it from locking by quickly moving my mouse over to the linux client. Would be great to have a feature that prevents the need for this action!

gitea-mirror commented

2026-05-05 05:22:50 -06:00

Author

Owner

@imsys commented on GitHub (Jul 9, 2020):

I found about Berrier today, installed the server on my Linux laptop, and used the Windows PC as a client.
As my laptop use less energy and doesn't produce noise, I usually don't power it off, so I decided to set it as the server.
I let most of my security sensitive stuff on my Linux and I like to let the screen locked when not working on it, but with Berrier doesn't work with my Linux screen locked.
I tried with in my Arch XFCE desktop, with light-locker, xfce4-screensaver, xscreensaver, gnome-screensaver, slock and xlockmore. All of those did not let me move the mouse to the Windows Client.

I wonder what could be done to allow it: I wonder if it was directly restricted in Barrier, or if it is the screenlockers softwares' restriction.

@imsys commented on GitHub (Jul 9, 2020): I found about Berrier today, installed the server on my Linux laptop, and used the Windows PC as a client. As my laptop use less energy and doesn't produce noise, I usually don't power it off, so I decided to set it as the server. I let most of my security sensitive stuff on my Linux and I like to let the screen locked when not working on it, but with Berrier doesn't work with my Linux screen locked. I tried with in my Arch XFCE desktop, with light-locker, xfce4-screensaver, xscreensaver, gnome-screensaver, slock and xlockmore. All of those did not let me move the mouse to the Windows Client. I wonder what could be done to allow it: I wonder if it was directly restricted in Barrier, or if it is the screenlockers softwares' restriction.

gitea-mirror commented

2026-05-05 05:22:52 -06:00

Author

Owner

@DragoonAethis commented on GitHub (Jul 9, 2020):

I'd say that the point of a screen locker is to prevent any sort of interaction with a host until you've unlocked it :P At least on Linux + X11, screen lockers will grab all input and prevent any background apps (such as Barrier) from handling it.

@DragoonAethis commented on GitHub (Jul 9, 2020): I'd say that the point of a screen locker is to prevent any sort of interaction with a host until you've unlocked it :P At least on Linux + X11, screen lockers will grab all input and prevent any background apps (such as Barrier) from handling it.

gitea-mirror commented

2026-05-05 05:22:54 -06:00

Author

Owner

@wokawoka commented on GitHub (Mar 22, 2023):

any news on this?

@wokawoka commented on GitHub (Mar 22, 2023): any news on this?

gitea-mirror commented

2026-05-05 05:22:57 -06:00

Author

Owner

@Revadike commented on GitHub (Jul 5, 2023):