Barrier: can’t lock the screen on a Windows client with Windows+L

[delan]

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

[sikandaramin]

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.

[spikefire]

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

[wjtk4444]

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.

[truatpasteurdotfr]

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).

[maverickr77]

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

[spikefire]

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

[wjtk4444]

@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.

[maverickr77]

@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.

[maverickr77]

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/