github-starred/barrier

Fork 0

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

[GH-ISSUE #541] Hitting Windows key while client is focused results in both client and Linux server responding #423

New issue

Open

opened 2026-05-05 06:21:27 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:21:27 -06:00

Owner

Originally created by @GitHubRub on GitHub (Jan 11, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/541

Operating Systems

Server: Kubuntu 19.10

Client: Windows 7

Barrier Version

2.3.2 Stable on both machines

Steps to reproduce bug

Move mouse cursor to client monitor.
Press Windows key.
Client PC brings up Start menu, but...
Server PC also brings up application launcher.

NOTE: other commands that use the Windows key (such as Win + Tab for shifting through windows and Win + Up to resize current window) are correctly only acknowledged by the client, not the server. It is only pressing the Windows key by itself that incorrectly causes the Linux server to respond.

Other info

When did the problem start to occur?
As soon as I started using barrier.
Is there a way to work around it?
Not that I've found.
Does this bug prevent you from using Barrier entirely?
Not yet.

Originally created by @GitHubRub on GitHub (Jan 11, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/541 ### Operating Systems ### Server: Kubuntu 19.10 Client: Windows 7 ### Barrier Version ### 2.3.2 Stable on both machines ### Steps to reproduce bug ### 1. Move mouse cursor to client monitor. 2. Press Windows key. 3. Client PC brings up Start menu, but... 4. Server PC also brings up application launcher. **NOTE:** other commands that use the Windows key (such as Win + Tab for shifting through windows and Win + Up to resize current window) are correctly only acknowledged by the client, not the server. It is only pressing the Windows key by itself that incorrectly causes the Linux server to respond. ### Other info ### * When did the problem start to occur? As soon as I started using barrier. * Is there a way to work around it? Not that I've found. * Does this bug prevent you from using Barrier entirely? Not yet.

gitea-mirror commented

2026-05-05 06:21:30 -06:00

Author

Owner

@estebanfeldman commented on GitHub (Jan 16, 2020):

Same happens to me with MacOS client and Windows 10 as server... if MacOS I hit Windows Key + L in Firefox (to focus the address bar) it will Lock the Windows 10 server, in Windows 10 Windows Key + L is Lock machine.

v2.3.2

Also in MacOS my Command and Option keys switched places.

@estebanfeldman commented on GitHub (Jan 16, 2020): Same happens to me with MacOS client and Windows 10 as server... if MacOS I hit Windows Key + L in Firefox (to focus the address bar) it will Lock the Windows 10 server, in Windows 10 Windows Key + L is Lock machine. v2.3.2 Also in MacOS my Command and Option keys switched places.

gitea-mirror commented

2026-05-05 06:21:34 -06:00

Author

Owner

@kepi commented on GitHub (Sep 4, 2020):

Win + L is driving me crazy as I'm using it on client to move to right workspace and it always locks the server (windows) and move me there. For me, it unfortunately makes barrier unusable at the moment :(

@kepi commented on GitHub (Sep 4, 2020): `Win + L` is driving me crazy as I'm using it on client to move to right workspace and it always locks the server (windows) and move me there. For me, it unfortunately makes barrier unusable at the moment :(

No labels

Rows
Columns