github-starred/barrier

Fork 0

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

[GH-ISSUE #776] Can't type on anything else but English #611

New issue

Open

opened 2026-05-05 06:46:44 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 06:46:44 -06:00

Owner

Originally created by @cyanoger on GitHub (Jul 1, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/776

Operating Systems

Server: Windows 10 Pro 64-bit, Version 2004, OS Build 19041.329

Client: Windows 10 Pro Educational 64-bit, Version 1909, OS Build 18363.719

Barrier Version

2.3.2-snapshot-210c2b70
(aka last stable build)

Steps to reproduce bug

Bug number one:

Switch to language other than English on host machine (Cyrillic is preferable, not cheked how other languages work)
Try to type anything on guest machine
Get nothing typed, aka get dead key syndrome.

Bug number two, less ridiculous:

Switch to language you want on guest machine
Try to type anything on guest machine using it
Get symbols typed with host-machine language layout

Other info

First bug began appearing after some minor windows update on 1909 vesrion of windows on guest machine. Second one appears always.
The only way to workaround first bug is to type transliteration of cyrillic text on guest or to type in cyrillic on host machine and copy-paste this text on guest machine.
You can workaround second bug by switching language only on host machine
I've tried reinstalling Barrier and even using older releases of it.
These bugs appear even when windows version match on both machines or when host version is lower than guest.
These bugs don't prevent me from using Barrier entirely.

Originally created by @cyanoger on GitHub (Jul 1, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/776 ### Operating Systems ### Server: Windows 10 Pro 64-bit, Version 2004, OS Build 19041.329 Client: Windows 10 Pro Educational 64-bit, Version 1909, OS Build 18363.719 ### Barrier Version ### 2.3.2-snapshot-210c2b70 (aka last stable build) ### Steps to reproduce bug ### Bug number one: 1. Switch to language other than English on host machine (Cyrillic is preferable, not cheked how other languages work) 2. Try to type anything on guest machine 3. Get nothing typed, aka get dead key syndrome. Bug number two, less ridiculous: 1. Switch to language you want on guest machine 2. Try to type anything on guest machine using it 3. Get symbols typed with host-machine language layout ### Other info ### * First bug began appearing after some minor windows update on 1909 vesrion of windows on guest machine. Second one appears always. * The only way to workaround first bug is to type transliteration of cyrillic text on guest or to type in cyrillic on host machine and copy-paste this text on guest machine. * You can workaround second bug by switching language only on host machine * I've tried reinstalling Barrier and even using older releases of it. * These bugs appear even when windows version match on both machines or when host version is lower than guest. * These bugs don't prevent me from using Barrier entirely.

gitea-mirror commented

2026-05-05 06:46:47 -06:00

Author

Owner

@cyanoger commented on GitHub (Jul 10, 2020):

https://support.symless.com/hc/en-us/articles/360007325517-International-Keyboard-Restrictions
I guess it might be something related to Synergy bug fixes, and we must wait for them to release everything at synergy core, right?

@cyanoger commented on GitHub (Jul 10, 2020): https://support.symless.com/hc/en-us/articles/360007325517-International-Keyboard-Restrictions I guess it might be something related to Synergy bug fixes, and we must wait for them to release everything at synergy core, right?

gitea-mirror commented

2026-05-05 06:46:48 -06:00

Author

Owner

@cyanoger commented on GitHub (Jul 28, 2020):

2.3.3 - still present

@cyanoger commented on GitHub (Jul 28, 2020): 2.3.3 - still present

gitea-mirror commented

2026-05-05 06:46:50 -06:00

Author

Owner

@shymega commented on GitHub (Jul 28, 2020):

https://support.symless.com/hc/en-us/articles/360007325517-International-Keyboard-Restrictions
I guess it might be something related to Synergy bug fixes, and we must wait for them to release everything at synergy core, right?

No. We don't generally merge commits from Synergy Core, as we forked from Synergy 2.x - I think, and don't follow their commits generally. We could look into cherry-picking commits from their fix, I suppose, but that would require further discussion: @p12tic - thoughts?

@shymega commented on GitHub (Jul 28, 2020): > https://support.symless.com/hc/en-us/articles/360007325517-International-Keyboard-Restrictions > I guess it might be something related to Synergy bug fixes, and we must wait for them to release everything at synergy core, right? No. We don't generally merge commits from Synergy Core, as we forked from Synergy 2.x - I think, and don't follow their commits generally. We could look into cherry-picking commits from their fix, I suppose, but that would require further discussion: @p12tic - thoughts?

gitea-mirror commented

2026-05-05 06:46:51 -06:00

Author

Owner

@shymega commented on GitHub (Jul 28, 2020):

2.3.3 - still present

Thanks for the update 👍

@shymega commented on GitHub (Jul 28, 2020): > 2.3.3 - still present Thanks for the update :+1:

gitea-mirror commented

2026-05-05 06:46:54 -06:00

Author

Owner

@ghost commented on GitHub (Jul 29, 2020):

Hi,

I have a similar issue but this time it's between English keyboards.

Server: Mac OS X 10.15.6, Barrier 2.3.2
Client: OpenBSD 6.7, Barrier 2.3.2

Both server and client are using British (English) keyboards, but on the Mac (which is the server in this case).. when I type ~ on the Mac, is comes out on the barrier client as |. Shift-3 which should be £ comes out as #. So it looks like on the barrier client the keyboard type is set to U.S.

I don't see any option to change this in the barrier server setup on the Mac, nor is there any option in the barrier client options on OpenBSD.

@ghost commented on GitHub (Jul 29, 2020): Hi, I have a similar issue but this time it's between English keyboards. Server: Mac OS X 10.15.6, Barrier 2.3.2 Client: OpenBSD 6.7, Barrier 2.3.2 Both server and client are using British (English) keyboards, but on the Mac (which is the server in this case).. when I type `~` on the Mac, is comes out on the barrier client as `|`. Shift-3 which should be `£` comes out as `#`. So it looks like on the barrier client the keyboard type is set to U.S. I don't see any option to change this in the barrier server setup on the Mac, nor is there any option in the barrier client options on OpenBSD.

gitea-mirror commented

2026-05-05 06:46:57 -06:00

Author

Owner

@hookedalready commented on GitHub (Aug 22, 2020):

Hello, i am on arch32 (client) and windows10 (host), using english and spanish, at first worked fine, then dead keys on spanish keyboard appearded(accent key and "ñ", not responding at all on the client machine) , it is barrier version 2.3.3. I has reinstalled the program and tried to clean regs on windows but nope

@hookedalready commented on GitHub (Aug 22, 2020): Hello, i am on arch32 (client) and windows10 (host), using english and spanish, at first worked fine, then dead keys on spanish keyboard appearded(accent key and "ñ", not responding at all on the client machine) , it is barrier version 2.3.3. I has reinstalled the program and tried to clean regs on windows but nope

gitea-mirror commented

2026-05-05 06:47:00 -06:00

Author

Owner

@hookedalready commented on GitHub (Aug 22, 2020):

nvm it is working again after set the spanish keyboard with setxkbmap on the arch

@hookedalready commented on GitHub (Aug 22, 2020): nvm it is working again after set the spanish keyboard with setxkbmap on the arch

gitea-mirror commented

2026-05-05 06:47:02 -06:00

Author

Owner

@darkdragon-001 commented on GitHub (Oct 20, 2020):

This bug is already apparent in symless/synergy-core#4309 for about five years.

@darkdragon-001 commented on GitHub (Oct 20, 2020): This bug is already apparent in symless/synergy-core#4309 for about five years.

gitea-mirror commented

2026-05-05 06:47:04 -06:00

Author

Owner

@JohnnyBoomKek commented on GitHub (Nov 3, 2020):

Any fixes or workarounds? It's pretty much impossible to work in a duallingo environment. =(

@JohnnyBoomKek commented on GitHub (Nov 3, 2020): Any fixes or workarounds? It's pretty much impossible to work in a duallingo environment. =(

gitea-mirror commented

2026-05-05 06:47:06 -06:00

Author

Owner

@darkdragon-001 commented on GitHub (Dec 20, 2020):

See meta issue #45 and linked issues.

@darkdragon-001 commented on GitHub (Dec 20, 2020): See meta issue #45 and linked issues.