github-starred/barrier
2
0
Fork 0
mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00
Code Issues 1.0k Projects Packages Wiki Activity Actions

[GH-ISSUE #265] can’t lock the screen on a Windows client with Windows+L #214

New issue
Open
opened 2026-05-05 05:42:04 -06:00 by gitea-mirror · 11 comments
gitea-mirror commented 2026-05-05 05:42:04 -06:00
Owner
Copy link

Originally created by @delan on GitHub (Mar 10, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/265

Operating Systems

Server: NixOS 19.03pre170287.19eedaf867d

Client: Windows 1809 (17763.348)

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

  1. press Windows+L and notice that the client screen doesn’t lock
  2. press Windows+E and notice that Windows Explorer does open

Other info

  • bug doesn’t prevent me from using Barrier entirely
  • bug can be worked around by locking the screen through the start menu

Debug1-level server log (Windows+L)

[2019-03-11T03:14:03] DEBUG1: new mask: 0x0000
[2019-03-11T03:14:03] DEBUG1: event: KeyPress code=133, state=0x0000
[2019-03-11T03:14:03] DEBUG1: onKeyDown id=61419 mask=0x0000 button=0x0085
[2019-03-11T03:14:03] DEBUG1: send key down to "redmond" id=61419, mask=0x0000, button=0x0085
[2019-03-11T03:14:08] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:08] DEBUG1: event: KeyPress code=46, state=0x0040
[2019-03-11T03:14:08] DEBUG1: onKeyDown id=108 mask=0x0010 button=0x002e
[2019-03-11T03:14:08] DEBUG1: send key down to "redmond" id=108, mask=0x0010, button=0x002e
[2019-03-11T03:14:08] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:08] DEBUG1: event: KeyRelease code=46, state=0x0040
[2019-03-11T03:14:08] DEBUG1: onKeyUp id=108 mask=0x0010 button=0x002e
[2019-03-11T03:14:08] DEBUG1: send key up to "redmond" id=108, mask=0x0010, button=0x002e
[2019-03-11T03:14:10] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:10] DEBUG1: event: KeyRelease code=133, state=0x0040
[2019-03-11T03:14:10] DEBUG1: onKeyUp id=61419 mask=0x0010 button=0x0085
[2019-03-11T03:14:10] DEBUG1: send key up to "redmond" id=61419, mask=0x0010, button=0x0085

Debug1-level client log (Windows+L)

[2019-03-11T03:14:04] DEBUG1: recv key down id=0x0000efeb, mask=0x0000, button=0x0085
[2019-03-11T03:14:04] DEBUG1: mapKey efeb (61419) with mask 0000, start state: 0000
[2019-03-11T03:14:04] DEBUG1: find best:  0000 0000
[2019-03-11T03:14:04] DEBUG1: best key index 1 of 1 (exact)
[2019-03-11T03:14:04] DEBUG1: found key in group 0
[2019-03-11T03:14:04] DEBUG1: state: 0000,0000,0000
[2019-03-11T03:14:04] DEBUG1: flip: 0000 (0000 vs 0000 in 0000 - 0000)
[2019-03-11T03:14:04] DEBUG1: desired state: 0000 0000,0000,0000
[2019-03-11T03:14:04] DEBUG1: flip: 0000 (0000 vs 0000 in ffef - 6020)
[2019-03-11T03:14:04] DEBUG1: mapped to 15b, new state 0010
[2019-03-11T03:14:04] DEBUG1: keystrokes:
[2019-03-11T03:14:04] DEBUG1:   15b (0000005b) down
[2019-03-11T03:14:09] DEBUG1: recv key down id=0x0000006c, mask=0x0010, button=0x002e
[2019-03-11T03:14:09] DEBUG1: mapKey 006c (108) with mask 0010, start state: 0010
[2019-03-11T03:14:09] INFO: found key in group 0
[2019-03-11T03:14:09] DEBUG1: state: 0010,0000,0000
[2019-03-11T03:14:09] DEBUG1: flip: 0000 (0010 vs 0000 in 0000 - 0000)
[2019-03-11T03:14:09] DEBUG1: desired state: 0010 0010,0000,1007
[2019-03-11T03:14:09] DEBUG1: flip: 0000 (0010 vs 0010 in ffff - 6020)
[2019-03-11T03:14:09] DEBUG1: mapped to 026, new state 0010
[2019-03-11T03:14:09] DEBUG1: keystrokes:
[2019-03-11T03:14:09] DEBUG1:   026 (0000004c) down
[2019-03-11T03:14:09] DEBUG1: recv key up id=0x0000006c, mask=0x0010, button=0x002e
[2019-03-11T03:14:09] DEBUG1: keystrokes:
[2019-03-11T03:14:09] DEBUG1:   026 (0000004c) up
[2019-03-11T03:14:11] DEBUG1: recv key up id=0x0000efeb, mask=0x0010, button=0x0085
[2019-03-11T03:14:11] DEBUG1: new state 0000
[2019-03-11T03:14:11] DEBUG1: keystrokes:
[2019-03-11T03:14:11] DEBUG1:   15b (0000005b) up

Debug1-level server log (Windows+E)

[2019-03-11T03:14:33] DEBUG1: new mask: 0x0000
[2019-03-11T03:14:33] DEBUG1: event: KeyPress code=133, state=0x0000
[2019-03-11T03:14:33] DEBUG1: onKeyDown id=61419 mask=0x0000 button=0x0085
[2019-03-11T03:14:33] DEBUG1: send key down to "redmond" id=61419, mask=0x0000, button=0x0085
[2019-03-11T03:14:33] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:33] DEBUG1: event: KeyPress code=26, state=0x0040
[2019-03-11T03:14:33] DEBUG1: onKeyDown id=101 mask=0x0010 button=0x001a
[2019-03-11T03:14:33] DEBUG1: send key down to "redmond" id=101, mask=0x0010, button=0x001a
[2019-03-11T03:14:34] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:34] DEBUG1: event: KeyRelease code=26, state=0x0040
[2019-03-11T03:14:34] DEBUG1: onKeyUp id=101 mask=0x0010 button=0x001a
[2019-03-11T03:14:34] DEBUG1: send key up to "redmond" id=101, mask=0x0010, button=0x001a
[2019-03-11T03:14:34] DEBUG1: new mask: 0x0010
[2019-03-11T03:14:34] DEBUG1: event: KeyRelease code=133, state=0x0040
[2019-03-11T03:14:34] DEBUG1: onKeyUp id=61419 mask=0x0010 button=0x0085
[2019-03-11T03:14:34] DEBUG1: send key up to "redmond" id=61419, mask=0x0010, button=0x0085

Debug1-level client log (Windows+E)

[2019-03-11T03:14:34] DEBUG1: recv key down id=0x0000efeb, mask=0x0000, button=0x0085
[2019-03-11T03:14:34] DEBUG1: mapKey efeb (61419) with mask 0000, start state: 0000
[2019-03-11T03:14:34] DEBUG1: find best:  0000 0000
[2019-03-11T03:14:34] DEBUG1: best key index 1 of 1 (exact)
[2019-03-11T03:14:34] DEBUG1: found key in group 0
[2019-03-11T03:14:34] DEBUG1: state: 0000,0000,0000
[2019-03-11T03:14:34] DEBUG1: flip: 0000 (0000 vs 0000 in 0000 - 0000)
[2019-03-11T03:14:34] DEBUG1: desired state: 0000 0000,0000,0000
[2019-03-11T03:14:34] DEBUG1: flip: 0000 (0000 vs 0000 in ffef - 6020)
[2019-03-11T03:14:34] DEBUG1: mapped to 15b, new state 0010
[2019-03-11T03:14:34] DEBUG1: keystrokes:
[2019-03-11T03:14:34] DEBUG1:   15b (0000005b) down
[2019-03-11T03:14:34] DEBUG1: recv key down id=0x00000065, mask=0x0010, button=0x001a
[2019-03-11T03:14:34] DEBUG1: mapKey 0065 (101) with mask 0010, start state: 0010
[2019-03-11T03:14:34] INFO: found key in group 0
[2019-03-11T03:14:34] DEBUG1: state: 0010,0000,0000
[2019-03-11T03:14:34] DEBUG1: flip: 0000 (0010 vs 0000 in 0000 - 0000)
[2019-03-11T03:14:34] DEBUG1: desired state: 0010 0010,0000,1007
[2019-03-11T03:14:34] DEBUG1: flip: 0000 (0010 vs 0010 in ffff - 6020)
[2019-03-11T03:14:34] DEBUG1: mapped to 012, new state 0010
[2019-03-11T03:14:34] DEBUG1: keystrokes:
[2019-03-11T03:14:34] DEBUG1:   012 (00000045) down
[2019-03-11T03:14:34] DEBUG1: recv key up id=0x00000065, mask=0x0010, button=0x001a
[2019-03-11T03:14:34] DEBUG1: keystrokes:
[2019-03-11T03:14:34] DEBUG1:   012 (00000045) up
[2019-03-11T03:14:35] DEBUG1: recv key up id=0x0000efeb, mask=0x0010, button=0x0085
[2019-03-11T03:14:35] DEBUG1: new state 0000
[2019-03-11T03:14:35] DEBUG1: keystrokes:
[2019-03-11T03:14:35] DEBUG1:   15b (0000005b) up
Originally created by @delan on GitHub (Mar 10, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/265 ### Operating Systems ### Server: NixOS 19.03pre170287.19eedaf867d Client: Windows 1809 (17763.348) ### Barrier Version ### 2.1.0-RELEASE-0b2dfd80 ### Steps to reproduce bug ### 1. press Windows+L and notice that the client screen doesn’t lock 2. press Windows+E and notice that Windows Explorer does open ### Other info ### * bug doesn’t prevent me from using Barrier entirely * bug can be worked around by locking the screen through the start menu Debug1-level server log (Windows+L) ``` [2019-03-11T03:14:03] DEBUG1: new mask: 0x0000 [2019-03-11T03:14:03] DEBUG1: event: KeyPress code=133, state=0x0000 [2019-03-11T03:14:03] DEBUG1: onKeyDown id=61419 mask=0x0000 button=0x0085 [2019-03-11T03:14:03] DEBUG1: send key down to "redmond" id=61419, mask=0x0000, button=0x0085 [2019-03-11T03:14:08] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:08] DEBUG1: event: KeyPress code=46, state=0x0040 [2019-03-11T03:14:08] DEBUG1: onKeyDown id=108 mask=0x0010 button=0x002e [2019-03-11T03:14:08] DEBUG1: send key down to "redmond" id=108, mask=0x0010, button=0x002e [2019-03-11T03:14:08] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:08] DEBUG1: event: KeyRelease code=46, state=0x0040 [2019-03-11T03:14:08] DEBUG1: onKeyUp id=108 mask=0x0010 button=0x002e [2019-03-11T03:14:08] DEBUG1: send key up to "redmond" id=108, mask=0x0010, button=0x002e [2019-03-11T03:14:10] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:10] DEBUG1: event: KeyRelease code=133, state=0x0040 [2019-03-11T03:14:10] DEBUG1: onKeyUp id=61419 mask=0x0010 button=0x0085 [2019-03-11T03:14:10] DEBUG1: send key up to "redmond" id=61419, mask=0x0010, button=0x0085 ``` Debug1-level client log (Windows+L) ``` [2019-03-11T03:14:04] DEBUG1: recv key down id=0x0000efeb, mask=0x0000, button=0x0085 [2019-03-11T03:14:04] DEBUG1: mapKey efeb (61419) with mask 0000, start state: 0000 [2019-03-11T03:14:04] DEBUG1: find best: 0000 0000 [2019-03-11T03:14:04] DEBUG1: best key index 1 of 1 (exact) [2019-03-11T03:14:04] DEBUG1: found key in group 0 [2019-03-11T03:14:04] DEBUG1: state: 0000,0000,0000 [2019-03-11T03:14:04] DEBUG1: flip: 0000 (0000 vs 0000 in 0000 - 0000) [2019-03-11T03:14:04] DEBUG1: desired state: 0000 0000,0000,0000 [2019-03-11T03:14:04] DEBUG1: flip: 0000 (0000 vs 0000 in ffef - 6020) [2019-03-11T03:14:04] DEBUG1: mapped to 15b, new state 0010 [2019-03-11T03:14:04] DEBUG1: keystrokes: [2019-03-11T03:14:04] DEBUG1: 15b (0000005b) down [2019-03-11T03:14:09] DEBUG1: recv key down id=0x0000006c, mask=0x0010, button=0x002e [2019-03-11T03:14:09] DEBUG1: mapKey 006c (108) with mask 0010, start state: 0010 [2019-03-11T03:14:09] INFO: found key in group 0 [2019-03-11T03:14:09] DEBUG1: state: 0010,0000,0000 [2019-03-11T03:14:09] DEBUG1: flip: 0000 (0010 vs 0000 in 0000 - 0000) [2019-03-11T03:14:09] DEBUG1: desired state: 0010 0010,0000,1007 [2019-03-11T03:14:09] DEBUG1: flip: 0000 (0010 vs 0010 in ffff - 6020) [2019-03-11T03:14:09] DEBUG1: mapped to 026, new state 0010 [2019-03-11T03:14:09] DEBUG1: keystrokes: [2019-03-11T03:14:09] DEBUG1: 026 (0000004c) down [2019-03-11T03:14:09] DEBUG1: recv key up id=0x0000006c, mask=0x0010, button=0x002e [2019-03-11T03:14:09] DEBUG1: keystrokes: [2019-03-11T03:14:09] DEBUG1: 026 (0000004c) up [2019-03-11T03:14:11] DEBUG1: recv key up id=0x0000efeb, mask=0x0010, button=0x0085 [2019-03-11T03:14:11] DEBUG1: new state 0000 [2019-03-11T03:14:11] DEBUG1: keystrokes: [2019-03-11T03:14:11] DEBUG1: 15b (0000005b) up ``` Debug1-level server log (Windows+E) ``` [2019-03-11T03:14:33] DEBUG1: new mask: 0x0000 [2019-03-11T03:14:33] DEBUG1: event: KeyPress code=133, state=0x0000 [2019-03-11T03:14:33] DEBUG1: onKeyDown id=61419 mask=0x0000 button=0x0085 [2019-03-11T03:14:33] DEBUG1: send key down to "redmond" id=61419, mask=0x0000, button=0x0085 [2019-03-11T03:14:33] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:33] DEBUG1: event: KeyPress code=26, state=0x0040 [2019-03-11T03:14:33] DEBUG1: onKeyDown id=101 mask=0x0010 button=0x001a [2019-03-11T03:14:33] DEBUG1: send key down to "redmond" id=101, mask=0x0010, button=0x001a [2019-03-11T03:14:34] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:34] DEBUG1: event: KeyRelease code=26, state=0x0040 [2019-03-11T03:14:34] DEBUG1: onKeyUp id=101 mask=0x0010 button=0x001a [2019-03-11T03:14:34] DEBUG1: send key up to "redmond" id=101, mask=0x0010, button=0x001a [2019-03-11T03:14:34] DEBUG1: new mask: 0x0010 [2019-03-11T03:14:34] DEBUG1: event: KeyRelease code=133, state=0x0040 [2019-03-11T03:14:34] DEBUG1: onKeyUp id=61419 mask=0x0010 button=0x0085 [2019-03-11T03:14:34] DEBUG1: send key up to "redmond" id=61419, mask=0x0010, button=0x0085 ``` Debug1-level client log (Windows+E) ``` [2019-03-11T03:14:34] DEBUG1: recv key down id=0x0000efeb, mask=0x0000, button=0x0085 [2019-03-11T03:14:34] DEBUG1: mapKey efeb (61419) with mask 0000, start state: 0000 [2019-03-11T03:14:34] DEBUG1: find best: 0000 0000 [2019-03-11T03:14:34] DEBUG1: best key index 1 of 1 (exact) [2019-03-11T03:14:34] DEBUG1: found key in group 0 [2019-03-11T03:14:34] DEBUG1: state: 0000,0000,0000 [2019-03-11T03:14:34] DEBUG1: flip: 0000 (0000 vs 0000 in 0000 - 0000) [2019-03-11T03:14:34] DEBUG1: desired state: 0000 0000,0000,0000 [2019-03-11T03:14:34] DEBUG1: flip: 0000 (0000 vs 0000 in ffef - 6020) [2019-03-11T03:14:34] DEBUG1: mapped to 15b, new state 0010 [2019-03-11T03:14:34] DEBUG1: keystrokes: [2019-03-11T03:14:34] DEBUG1: 15b (0000005b) down [2019-03-11T03:14:34] DEBUG1: recv key down id=0x00000065, mask=0x0010, button=0x001a [2019-03-11T03:14:34] DEBUG1: mapKey 0065 (101) with mask 0010, start state: 0010 [2019-03-11T03:14:34] INFO: found key in group 0 [2019-03-11T03:14:34] DEBUG1: state: 0010,0000,0000 [2019-03-11T03:14:34] DEBUG1: flip: 0000 (0010 vs 0000 in 0000 - 0000) [2019-03-11T03:14:34] DEBUG1: desired state: 0010 0010,0000,1007 [2019-03-11T03:14:34] DEBUG1: flip: 0000 (0010 vs 0010 in ffff - 6020) [2019-03-11T03:14:34] DEBUG1: mapped to 012, new state 0010 [2019-03-11T03:14:34] DEBUG1: keystrokes: [2019-03-11T03:14:34] DEBUG1: 012 (00000045) down [2019-03-11T03:14:34] DEBUG1: recv key up id=0x00000065, mask=0x0010, button=0x001a [2019-03-11T03:14:34] DEBUG1: keystrokes: [2019-03-11T03:14:34] DEBUG1: 012 (00000045) up [2019-03-11T03:14:35] DEBUG1: recv key up id=0x0000efeb, mask=0x0010, button=0x0085 [2019-03-11T03:14:35] DEBUG1: new state 0000 [2019-03-11T03:14:35] DEBUG1: keystrokes: [2019-03-11T03:14:35] DEBUG1: 15b (0000005b) up ```
gitea-mirror added the
bug
windows
linux
 labels 2026-05-05 05:42:04 -06:00
gitea-mirror commented 2026-05-05 05:42:07 -06:00
Author
Owner
Copy link

@sikandaramin commented on GitHub (Aug 7, 2019):

Did someone get the solution to this issue??

I can confirm this exact problem.
Moreover, ctrl+alt+del also doesn't work on client machine.

<!-- gh-comment-id:519093041 --> @sikandaramin commented on GitHub (Aug 7, 2019): **Did someone get the solution to this issue??** I can confirm this exact problem. Moreover, **ctrl+alt+del** also doesn't work on client machine.
gitea-mirror commented 2026-05-05 05:42:10 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Aug 28, 2019):

I also have this issue.
Server operating system: Ubuntu Mate 19.04
Client operating system: Windows 10 1809

<!-- gh-comment-id:525912317 --> @ghost commented on GitHub (Aug 28, 2019): I also have this issue. Server operating system: Ubuntu Mate 19.04 Client operating system: Windows 10 1809
gitea-mirror commented 2026-05-05 05:42:12 -06:00
Author
Owner
Copy link

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

I can lock my windows client using Win+L.
Barrier 2.1.2-2 on Arch Linux
Barrier 2.3.0-snapshot-8e8b38b4 on Windows 7

I think it works on all barrier versions, the only reason I have 2.3.0-snapshot installed is because I was testing something else in the past and it just stayed like this.

<!-- gh-comment-id:532711927 --> @wjtk4444 commented on GitHub (Sep 18, 2019): I **can** lock my windows client using Win+L. Barrier 2.1.2-2 on Arch Linux Barrier 2.3.0-snapshot-8e8b38b4 on Windows 7 I think it works on all barrier versions, the only reason I have 2.3.0-snapshot installed is because I was testing something else in the past and it just stayed like this.
gitea-mirror commented 2026-05-05 05:42:13 -06:00
Author
Owner
Copy link

@truatpasteurdotfr commented on GitHub (Sep 22, 2019):

I can also lock win10 x64 client (barriersetup-2.3.1-release.exe on Microsoft Windows [version 10.0.18362.356] ) from a CentOS-7 client x86_64 (barrier 2.3.1 git 0ed18c6b).

<!-- gh-comment-id:533913732 --> @truatpasteurdotfr commented on GitHub (Sep 22, 2019): I can also lock win10 x64 client (barriersetup-2.3.1-release.exe on Microsoft Windows [version 10.0.18362.356] ) from a CentOS-7 client x86_64 (barrier 2.3.1 git 0ed18c6b).
gitea-mirror commented 2026-05-05 05:42:14 -06:00
Author
Owner
Copy link

@maverickr77 commented on GitHub (Jan 23, 2020):

I was seeing the same problem where CTRL+ALT+DLT wasn't working on a Windows 10 client (with Centos 7.7 Server).

It seems like this problem was addressed in Synergy 1.0. The workaround of updating the Windows Logon Options as suggested here works for me!

With this change, my Client now responds to both CTRL+ALT+DLT and CTRL+ALT+PAUSE/BREAK

https://github.com/symless/synergy-core/wiki/Core-User-FAQ#Why_doesnt_CtrlAltDel_work_on_secondary_screens

<!-- gh-comment-id:577699854 --> @maverickr77 commented on GitHub (Jan 23, 2020): I was seeing the same problem where CTRL+ALT+DLT wasn't working on a Windows 10 client (with Centos 7.7 Server). It seems like this problem was addressed in Synergy 1.0. The workaround of updating the Windows Logon Options as suggested here works for me! With this change, my Client now responds to both CTRL+ALT+DLT and CTRL+ALT+PAUSE/BREAK https://github.com/symless/synergy-core/wiki/Core-User-FAQ#Why_doesnt_CtrlAltDel_work_on_secondary_screens
gitea-mirror commented 2026-05-05 05:42:16 -06:00
Author
Owner
Copy link

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

Thanks, maverickr77. That fixed the Ctrl-Alt-Del issue.

Still not able to lock Windows by using Windowskey+L.

I am using Ubuntu 19.10 Barrier Server
and Windows 10 1909 Barrier Client

<!-- gh-comment-id:577724063 --> @ghost commented on GitHub (Jan 23, 2020): Thanks, maverickr77. That fixed the Ctrl-Alt-Del issue. Still not able to lock Windows by using Windowskey+L. I am using Ubuntu 19.10 Barrier Server and Windows 10 1909 Barrier Client
gitea-mirror commented 2026-05-05 05:42:19 -06:00
Author
Owner
Copy link

@wjtk4444 commented on GitHub (Jan 23, 2020):

@maverickr77
Could you tell me if print screen works normally for you? Mine is being recognized as alt + print screen for some reason.

I'm using the following on windows 7 client (without that Polish characters (altgr + a, s, c, etc...) don't work), but even without it I'm getting the same print screen behaviour.

        meta = altgr
        altgr = shift

Also, do you by chance use meta to open "start menu" on your server? On mine I'm running KDE with windows-like key shortcuts. Whenever I press meta on client, the "start menu" opens both on client and server. I'd like to know if it's KDE specific bug or an issue with barrier.

<!-- gh-comment-id:577822005 --> @wjtk4444 commented on GitHub (Jan 23, 2020): @maverickr77 Could you tell me if print screen works normally for you? Mine is being recognized as alt + print screen for some reason. I'm using the following on windows 7 client (without that Polish characters (altgr + a, s, c, etc...) don't work), but even without it I'm getting the same print screen behaviour. ``` meta = altgr altgr = shift ``` Also, do you by chance use meta to open "start menu" on your server? On mine I'm running KDE with windows-like key shortcuts. Whenever I press meta on client, the "start menu" opens both on client and server. I'd like to know if it's KDE specific bug or an issue with barrier.
gitea-mirror commented 2026-05-05 05:42:21 -06:00
Author
Owner
Copy link

@maverickr77 commented on GitHub (Jan 23, 2020):

@wjtk4444 I'm seeing the same issue on my Windows 10 client. This seems to be a general issue with barrier.

Print screen doesn't grab the full screen, if atleast one window is open on my screen. It only grabs the active window. (ALT + Print Screen behavior)

However if no windows are open on the screen, Print Screen grabs the full screen.

I don't use meta or any other modifier keys or shortcuts.

<!-- gh-comment-id:577826810 --> @maverickr77 commented on GitHub (Jan 23, 2020): @wjtk4444 I'm seeing the same issue on my Windows 10 client. This seems to be a general issue with barrier. Print screen doesn't grab the full screen, if atleast one window is open on my screen. It only grabs the active window. (ALT + Print Screen behavior) However if no windows are open on the screen, Print Screen grabs the full screen. I don't use meta or any other modifier keys or shortcuts.
gitea-mirror commented 2026-05-05 05:42:22 -06:00
Author
Owner
Copy link

@maverickr77 commented on GitHub (Jan 23, 2020):

Looks like this is an open issue in Synergy 1.x
https://members.symless.com/forums/topic/5784-print-screen-not-working-on-w10-client-pc-takes-it-as-alt/

<!-- gh-comment-id:577836011 --> @maverickr77 commented on GitHub (Jan 23, 2020): Looks like this is an open issue in Synergy 1.x https://members.symless.com/forums/topic/5784-print-screen-not-working-on-w10-client-pc-takes-it-as-alt/
gitea-mirror commented 2026-05-05 05:42:25 -06:00
Author
Owner
Copy link

@danielkrajnik commented on GitHub (Dec 28, 2021):

how do you lock windows 10 in general without neither ctrl+alt+delete nor Super Key+L. The only other solution was a not recommended "C:\Windows\System32\rundll32.exe user32.dll,LockWorkStation" command.

Can "lock" entry be brought back to the main menu in windows 10?

EDIT: found out that "locking buttton" in windows is located in the main menu under "user icon"

<!-- gh-comment-id:1002273664 --> @danielkrajnik commented on GitHub (Dec 28, 2021): how do you lock windows 10 in general without neither ctrl+alt+delete nor Super Key+L. The only other solution was a not recommended "C:\Windows\System32\rundll32.exe user32.dll,LockWorkStation" command. Can "lock" entry be brought back to the main menu in windows 10? EDIT: found out that "locking buttton" in windows is located in the main menu under "user icon"
gitea-mirror commented 2026-05-05 05:42:29 -06:00
Author
Owner
Copy link

@coryw commented on GitHub (Feb 9, 2023):

For anyone wanting a quick and easy way to lock your computer with the keyboard, I created a shortcut with the target set as C:\Windows\System32\rundll32.exe user32.dll,LockWorkStation as @danielkrajnik mentioned and placed it in the taskbar. Now I can use Windows Key + 7 to lock my screen.

<!-- gh-comment-id:1424208344 --> @coryw commented on GitHub (Feb 9, 2023): For anyone wanting a quick and easy way to lock your computer with the keyboard, I created a shortcut with the target set as `C:\Windows\System32\rundll32.exe user32.dll,LockWorkStation` as @danielkrajnik mentioned and placed it in the taskbar. Now I can use `Windows Key + 7` to lock my screen.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
enhancement/builds/windows-multi-versions-build
martin-furter-barrier-term
enhancement/builds/macos-universal
enhancement/builds/macos-universal-qt6-test
2.3.x
fix/lang-translation/ssl-slash-tls
feature/build/compile/32-bit
feature/build/compile/armv7
testing-framework
README-update
remotes/fork/README-update
remotes/fork/smartzeroconf
smartzeroconf
pages-devel
remotes/fork/pages-devel
pkgconfig
remotes/fork/pkgconfig
release
remotes/fork/release
v2.4.0
v2.3.4
v2.3.3
1.11.0-stable
v1.11.0-rc2
v2.3.2
v1.10.3-stable
v2.3.2-alpha
v2.3.1
v2.3.0
v1.10.2-stable
v1.10.2-rc1
v1.10.2-rc2
v2.1.2
v2.0.8-beta
v2.0.7-beta
v2.0.4-beta
v2.0.3-beta
v2.1.1
v2.1.0
v1.9.1-stable
v2.0.0
v1.9.0-stable
v2.0.0-RC2
v2.0.0-RC1
v2.0.0-stable
v1.8.8-stable
v1.8.7-stable
v1.8.6-stable
v1.8.5-stable
v1.8.4-stable
v1.8.3-stable
v1.8.1-stable
v1.8.0-beta
v1.7.3-stable
v1.7.2-stable
v1.7.1-stable
1.7.0
1.6.3-final
1.6.2
1.6.1
1.6.0
Labels
Clear labels   
HiDPI

   
bounty

   
bsd/freebsd

   
bsd/openbsd

   
bug

   
bug

   
build-infra

   
cantfix

   
critical

   
doc

   
duplicate

   
enhancement

   
fix-available

   
from git

   
from release

   
good first issue

   
help wanted

   
installer/package

   
invalid

   
linux

   
macOS

   
meta

   
needs testing

   
pull-request

Mirrored from GitHub Pull Request

  
query

   
question

   
regression

   
regression

   
v2.4.0

   
windows

   
wontfix

   
work-in-progress
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#214
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?