mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #532] Some keyboard strokes are not working properly #417
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#417
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @EmilianoTalamo on GitHub (Dec 23, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/532
Operating Systems
Server: Windows 10
Client: Mac OS Mojave
Barrier Version
2.3.2
Bug Info
I have an US International keyboard layout on both server and client. Most of the keys are working properly, but some there are a few that are acting weirdly or not working at all:
I'm using the Ukelele App to check which keys are being detected by the client.
@EmilianoTalamo commented on GitHub (Dec 30, 2019):
Update: This error shows up in the log of the client every time I press the single quote key:
barrierc[23501:716161] pid(23501)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!@SebastianGrans commented on GitHub (Mar 4, 2020):
I also have some problems.
The Mac is the client with the following mapping:
On a Mac (with swedish keyboard layout) you write a backslash using
Shift-Option-7, (withoptionbeing thealtequivalent). After pressingshift-altnothing gets detected.Another thing: when pressing
alt-7it somehow gets mapped to the equivalent toOption-8on the Mac, when in fact I expected it to beOption-7which should give me a pipe|.This is most likely related to issue #527.
@alessandro-lenzi commented on GitHub (Apr 18, 2020):
On US-Intl layouts to have:
@devilish2o commented on GitHub (May 4, 2020):
Having exactly the same problem, using this excellent piece of software on windows 10, raspbian and osx at the same time, win 10 is the server and a bluetooth keyboard is connected to it, using international us.
I have to omit the single quote if i don't (argh!!!!) want to move back to mac keyboard. Is there an easier work around?
Many thanks again :)
@alessandro-lenzi commented on GitHub (Jun 17, 2020):
#653
Downloaded this build artifact directly from Azure Pipelines while it's still not published and it worked:
https://dev.azure.com/debauchee/Barrier/_build/results?buildId=252&view=artifacts&type=publishedArtifacts
Just installed on my Windows 10 (Barrier server) and those quotes/double-quotes began to work properly on my Mac by using the "Brazillian" layout (not Brazillian ABNT2 or Brazillian Pro).
@gustavostugova commented on GitHub (Jun 6, 2021):
I experienced the same issue today, with server running on OSX, and controlling a Windows 10 PC. On both sides I have United States (international) layout. I think it was working fine, and suddenly stopped for those keys / characters.
Anyway, I think the problem is some kind of collision between both systems requiring the +[space] combination. When I configured the keyboard on the PC with another layout (in my case, English - United Kingdom, that is the layout of the Windows 10 Notebook I'm using and controlling from OSX), the problem disappears.
I hope this helps you.
@enricodias commented on GitHub (Jun 7, 2021):
Same issue here. Changing the keyboard layout to UK have no effect. Quotes are one of the most used characters in programming. It's literally impossible to work without it.
@gustavostugova commented on GitHub (Jun 7, 2021):
The solution is not because of the "UK", I think, but because of the
deactivation of the "international" mode. I changed on my client from "EEUU
issue occurs when [Quote+Space] is in use on both sides simultaneously
(Server and Client).
On Mon, 7 Jun 2021 at 12:05, Enrico Dias @.***> wrote:
@enricodias commented on GitHub (Jun 7, 2021):
I just managed to make it work here by restarting barrier on both the client and the server after changing the keyboard layouts. Really strange issue.
@zsoltszakaly commented on GitHub (Jul 31, 2021):
I have a similar issue. On international keyboards (HU) on both server and client most of the special characters work, but two does not. Alt-Gr í (yes it is the 102nd key, with a special character by itself) should be <, but instead it is >. Alt-Gr c (that is at least a normal character) should be &, but I get ł. In the log of the client I see INFO: found key in group 0, but apparently it finds the wrong key.
@gustavostugova commented on GitHub (Jul 31, 2021):
After a lot of trial and error, I ended with the following setup:
Server running on OSX. Keyboard configured as "U.S. - International". With
focus on the OSX, when I type 'a, I get á, when I type ~n, I get ñ....
etc. Everything works fine.
When I switch to focus on a client running windows, everything works OK
there too. The same key combination works fine there. In one client, I
noted that, if I have both layouts enabled on that client, (US, and
US-International), it doesn't matter which one is currently selected
there, when I hit the 'a combination (or similar combinations), I get an
á (or the corresponding expected result), and at the same time the layout
there switches to US-International, if it was not already there.
The problem occurs when, from one of the windows clients, I need to connect
to another windows machine via RDP. In that case, things start to work a
little weird. Some combinations still work.... but others are triggering
menus, or other actions. In notepad for example, I can write á, é, ú.....
but not í or ó..... sometimes.... and sometimes, it is the inverse. If I
hit '+[space] ..... after that, it gets even more weird. The combination
'a produces [a, 'e produces [e.... and so on. It's pretty eratical.
Some combinations even produce different results if hitted repeatedly. The
solution in that case is: on de Mac, switch from "U.S. - International" to
just "US", When I do that, I lose in the mac the combinations 'a 'e 'i 'o
'u to produce á é í ó ú, and even I lose the same combinations on my win
clients, but at the same time, on the Win via RDP from one of my Win
clients, everything starts working fine. If I already entered in the "wrong
mode" there (on de RDP), that produces [a [e [i [o [u, or If I'm getting -a
-e -i -o -u.... I fix that by hitting AltGR`` and that solves the
misconfiguration again.
Not and easy ride, but I still consider this better than a hardware KVM.
Good luck!
On Sat, 31 Jul 2021 at 06:58, zsoltszakaly @.***> wrote:
@anarqz commented on GitHub (Sep 13, 2021):
Just leaving my workaround for the QUOTES issue here. My keyboard is US but as I'm from brazil I need to use acentos. Like ã, á and of course quotes " ' ` . .... So what worked for me, was:
Server: Windows
Keyboard Layouts:
Client: Mac
Keyboard Layouts:
After restarting both machines, putting Mac on BRITISH layout. Start barrier on both machines and change Mac layout to US INTERNATIONAL - PC.
Bang! Both, acentos and quotes working as expected.
Would be nice to have this bug fixed, tho.
@eusgit commented on GitHub (Oct 3, 2021):
I confirm the same issue.
Barrier server: iMac (I had US-International Input source as primary, Italian as the second language)
Barrier client: MacBook (I had US-International Input source)
I have solved as follow:
And now it works properly.
(Also It's working when I add the second language for server input source)
@fypc commented on GitHub (Dec 5, 2021):
I confirm the same issue with ` and tilde characters not working on the barrier client with the dead key of the mac keyboard.
@luiscamaral commented on GitHub (Dec 5, 2021):
I also report a similar issue. US-International keyboard not working properly.
@luiscamaral commented on GitHub (Dec 5, 2021):
Is there a branch open to work out this issue ? Or is it on the roadmap of someone for soon work on it ?
@luiscamaral commented on GitHub (Dec 5, 2021):
I can confirm the workaround from @alcmoraes worked for me also. (Server: MacOS, Client: MacOS)
@dtangster commented on GitHub (Dec 22, 2021):
I'm also hitting the same issue where I can't type tilde (`).
@mvoelske commented on GitHub (Jan 5, 2022):
I think I have the same issue. I'm using:
us dvorak-intllayoutUnited States-Dvorak Internationallayout from keyboards.jargon-file.orgIn my case, sending single quotes to the client through barrier (
'followed byspacewith the deadkeys layout) works fine, as do single-accented letters (`or'followed by the letter). What doesn't work are double quote (shift+'followed byspace) or letters with diareses, neither does~.I checked with the tool from carnackeys.com -- it looks like when I press the deadkey for
', the client receives that keystroke immediately, whereas forshift+'or the~key, nothing is received, ever.@codearis commented on GitHub (Jan 22, 2022):
Thank you, this worked!
@imbdb commented on GitHub (Mar 30, 2022):
To resolve this
I just added hotkey for it
shift+~=>shift+~and same for backtick
@stefanhendriks commented on GitHub (May 12, 2022):
@imbdb - can't believe that worked. Tried everything with setting to same keyboard layout, nothing worked.
I use Mac OS 12.3.1 as server, and Windows 10 as client.
@pemora commented on GitHub (May 15, 2022):
I am also encountering the tilde and backtick issue. Everything was working fine before with a Mac Os Big Sur for the server and a Fedora 35 client.
After upgrading to monterey and fedora 36, things stopped working. Since I upgraded both stations on the same day, I'm not sure which one is causing the issue 😅
I tried @imbdb hotkeys trick, and it does now forward the tilde and backtick to Fedora, but they are not registered on Mac anymore, am I missing something? 😅
@stefanhendriks commented on GitHub (May 16, 2022):
Yes, I also noticed the backtick no longer works on the mac. I had to stop the Barrier server. Looks like the hotkey is always picked up, but somehow on my mac it did not translate to a backtick? Weird?
@bdmorin commented on GitHub (May 16, 2022):
thanks, worked like a charm.
@luiscamaral commented on GitHub (May 16, 2022):
I am not sure what the issue is, but I've been using a workaround that
works for me.
The workaround is to put the main (server) computer to sleep and then wake
it up after a few seconds and it starts to work again for all special
characters on 'US International' keyboard on the second computer.
MacOS x86 (server) ==> MacOS M1
*It's like this almost every morning for me. Kind of annoying but I got
used to it.
On Mon, May 16, 2022 at 2:20 PM Brian @.***> wrote:
@gustavostugova commented on GitHub (Jun 12, 2022):
The @imbdb solution with shortcuts, that didn't work ok for me. With this shortcuts, I get get intended characters on my client even when the focus is on the server. Also I lost the hability to write the intended characters on the server.
@gustavostugova commented on GitHub (Jun 13, 2022):
Found the solution:
Uninstall this, and install this version: https://github.com/DEAKSoftware/Synergy-Binaries/releases/tag/1.14.3.5-stable
@jgcl commented on GitHub (Jul 22, 2023):
I can confirm the workaround from @alcmoraes worked for me too. (Server: MacOS, Client: MacOS)
@boringparty commented on GitHub (Nov 1, 2023):
I personally fixed this using Keyboard Manager in Power Tools for Windows. I remapped VK243 to ` and made sure my language wasn't set to International, or else it'll be waiting for another character to be accented.
@rr-commits commented on GitHub (Jun 11, 2024):
Just had the same issue, wanting to use US International on both my Server and Client. The following setup worked for me:
Server: Windows (US-International)
Client: Mac (German Layout)
Now both client and server are using US international layout.
@DaniloReisRocha commented on GitHub (Oct 22, 2024):
I was having the same issue with a client and server on Windows 10. I solved it by stopping the client, adding the EU (international) and ABNT2 language options on the client PC, and then restarting Barrier. The server remained with only ABNT2.
