Server: Any (Linux?)
Client: Any (Windows?)
Any
I only use one language other than English, but I think that solving this issue could also close many others related to keyboard layouts and typing in non-latin characters.
Polish is written with the standardized Polish alphabet, which has nine additions to the letters of the basic Latin script (ą, ć, ę, ł, ń, ó, ś, ź, ż).
For instance, to type ą
, I have to press RALT+a
. It does work on the host, but it doesn't on the client. When I toggle the right alt manually (via on-screen keyboard), it works as expected.
I would suspect that Windows uses another keycode for RALT than Linux, and it simply ignores whatever is being sent.
key ef7e is not on keyboard
is what I get from DEBUG1 on client.
So, after (two?) years of using Barrier (and other syngery forks) almost everyday, I finally realized there's an option to configure it with a .conf file. Apparently, it allows one to remap keys at will. Well, better late than never.
Looking at some issue threads while also trying things out and failing (a lot), those are the two lines that fixed the issue. It looks like it makes no sense (if anything, I expected altgr = alt
to work instead of this), but it just works.
section: screens
linux:
windows7:
meta = altgr
altgr = shift
end
So, it seems that
Not sure if there's a point in keeping this one open - not a Barrier specific bug and it's already reported and described well enough in synergy-core. I'm leaving the decision on whether to close or keep this one open to repository maintainers.
@AdrianKoshka Does it make sense to close the issue?
I suppose so, if this issue needs to be re-opened, it can be.
This saved me from insanity.
For reference: I use a wired mac keyboard on a Linux server and mixed Windows10 / linux clients
Most helpful comment
So, after (two?) years of using Barrier (and other syngery forks) almost everyday, I finally realized there's an option to configure it with a .conf file. Apparently, it allows one to remap keys at will. Well, better late than never.
Looking at some issue threads while also trying things out and failing (a lot), those are the two lines that fixed the issue. It looks like it makes no sense (if anything, I expected
altgr = alt
to work instead of this), but it just works.So, it seems that
f@!#ing manualreadme file earlierNot sure if there's a point in keeping this one open - not a Barrier specific bug and it's already reported and described well enough in synergy-core. I'm leaving the decision on whether to close or keep this one open to repository maintainers.