[GH-ISSUE #1181] MacBook (as server) - Keyboard US International in both - Tilde don't work on Windows 10 (as client) #951

Open
opened 2026-05-05 07:19:15 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @LuizSiqueiraNeto on GitHub (Jun 2, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1181

MacBook (as server) - Keyboard US International in both - Tilde don't work on Windows 10 (as client).

Hitting Shift + (Grave key `) + (a or o), in both uppercase and lowercase, does nothing, it should generate the [ã or õ].
The dead key does not work for accents.

Captura de Tela 2021-06-02 às 10 50 29
Originally created by @LuizSiqueiraNeto on GitHub (Jun 2, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1181 **MacBook (as server) - Keyboard US International in both - Tilde don't work on Windows 10 (as client).** Hitting Shift + (Grave key `) + (a or o), in both uppercase and lowercase, does nothing, it should generate the [ã or õ]. The dead key does not work for accents. <img width="404" alt="Captura de Tela 2021-06-02 às 10 50 29" src="https://user-images.githubusercontent.com/40324430/120492703-ad971a00-c390-11eb-9119-090e39cd06cf.png">
Author
Owner

@jmahone commented on GitHub (Jun 2, 2021):

Saw this issue and wanted to test it since I have both macOS server and client. I am able to generate the ~ character as expected. I am running macOS 10.14.6 (Mojave) as the server and macOS 10.15.7 (Catalina) as the client.

I'm running Barrier v2.3.3-release-3395cca9 with Build Date: July 14, 2020

I'm using the US keyboard ( not US International), so I wonder if you have tried the straight US keyboard as a test to isolate the issue.

<!-- gh-comment-id:853072325 --> @jmahone commented on GitHub (Jun 2, 2021): Saw this issue and wanted to test it since I have both macOS server and client. I am able to generate the ~ character as expected. I am running macOS 10.14.6 (Mojave) as the server and macOS 10.15.7 (Catalina) as the client. I'm running Barrier v2.3.3-release-3395cca9 with Build Date: July 14, 2020 I'm using the US keyboard ( not US International), so I wonder if you have tried the straight US keyboard as a test to isolate the issue.
Author
Owner

@LuizSiqueiraNeto commented on GitHub (Jun 2, 2021):

Saw this issue and wanted to test it since I have both macOS server and client. I am able to generate the ~ character as expected. I am running macOS 10.14.6 (Mojave) as the server and macOS 10.15.7 (Catalina) as the client.

I'm running Barrier v2.3.3-release-3395cca9 with Build Date: July 14, 2020

I'm using the US keyboard ( not US International), so I wonder if you have tried the straight US keyboard as a test to isolate the issue.

I did a few more tests and realized that it's only when I try to write ã or õ, in both uppercase and lowercase, that it doesn't work. I updated my post to be better explained. Thanks for the feedback.

<!-- gh-comment-id:853204025 --> @LuizSiqueiraNeto commented on GitHub (Jun 2, 2021): > Saw this issue and wanted to test it since I have both macOS server and client. I am able to generate the ~ character as expected. I am running macOS 10.14.6 (Mojave) as the server and macOS 10.15.7 (Catalina) as the client. > > I'm running Barrier v2.3.3-release-3395cca9 with Build Date: July 14, 2020 > > I'm using the US keyboard ( not US International), so I wonder if you have tried the straight US keyboard as a test to isolate the issue. I did a few more tests and realized that it's only when I try to write ã or õ, in both uppercase and lowercase, that it doesn't work. I updated my post to be better explained. Thanks for the feedback.
Author
Owner

@wklaebe commented on GitHub (Jun 13, 2021):

I might have a similar problem... Devuan unstable on a Macbook as server, Raspberry OS bullseye on a Raspberry Pi 3 as client, Umlauts like äöüß don't arrive on client, | becomes , maybe more.

<!-- gh-comment-id:860263635 --> @wklaebe commented on GitHub (Jun 13, 2021): I might have a similar problem... Devuan unstable on a Macbook as server, Raspberry OS bullseye on a Raspberry Pi 3 as client, Umlauts like äöüß don't arrive on client, | becomes \, maybe more.
Author
Owner

@felixmagnus commented on GitHub (Sep 13, 2021):

I have a similar problem with äöü (German Layout), Windows (Server), Mac (Client), both version 2.3.3-release-3395cca9

This is the log (DEBUG1) on the server when I type ä:

[2021-09-13T09:20:10] DEBUG1: hook: 0x000000de 0x00280001
[2021-09-13T09:20:10] DEBUG1: hook: 0x0601e4de 0x00280001
[2021-09-13T09:20:10] DEBUG1: hook: 0x0700e4de 0x00280001
[2021-09-13T09:20:10] DEBUG1: event: Key char=228, vk=0xde, nagr=0, lParam=0x00280001
[2021-09-13T09:20:10] DEBUG1: new mask: 0x2000
[2021-09-13T09:20:10] DEBUG1: new mask: 0x2000
[2021-09-13T09:20:10] DEBUG1: onKeyDown id=65533 mask=0x2000 button=0x0028
[2021-09-13T09:20:10] DEBUG1: send key down to "MAC_OS" id=65533, mask=0x2000, button=0x0028
[2021-09-13T09:20:10] DEBUG1: hook: 0x000000de 0x80280001
[2021-09-13T09:20:10] DEBUG1: hook: 0x0601e4de 0x80280001
[2021-09-13T09:20:10] DEBUG1: hook: 0x0700e4de 0x80280001
[2021-09-13T09:20:10] DEBUG1: event: Key char=228, vk=0xde, nagr=0, lParam=0x80280001
[2021-09-13T09:20:10] DEBUG1: new mask: 0x2000
[2021-09-13T09:20:10] DEBUG1: new mask: 0x2000
[2021-09-13T09:20:10] DEBUG1: onKeyUp id=65533 mask=0x2000 button=0x0028
[2021-09-13T09:20:10] DEBUG1: send key up to "MAC_OS" id=65533, mask=0x2000, button=0x0028

It seems that ä gets mapped to 65533 which is https://www.fileformat.info/info/unicode/char/fffd/index.htm which maybe means that the character is not being interpreted correctly within the character encoding... (https://stackoverflow.com/questions/41462598/recieving-65533-as-char-value-for-characters-as-%C3%A0-%C3%98-%C3%A6-%C3%A6-etc)

But I'm not sure about this

I have not tried cloning the latest source and building it by hand on Win / Mac, maybe that helps...

<!-- gh-comment-id:917951020 --> @felixmagnus commented on GitHub (Sep 13, 2021): I have a similar problem with äöü (German Layout), Windows (Server), Mac (Client), both version 2.3.3-release-3395cca9 This is the log (DEBUG1) on the server when I type ä: ``` [2021-09-13T09:20:10] DEBUG1: hook: 0x000000de 0x00280001 [2021-09-13T09:20:10] DEBUG1: hook: 0x0601e4de 0x00280001 [2021-09-13T09:20:10] DEBUG1: hook: 0x0700e4de 0x00280001 [2021-09-13T09:20:10] DEBUG1: event: Key char=228, vk=0xde, nagr=0, lParam=0x00280001 [2021-09-13T09:20:10] DEBUG1: new mask: 0x2000 [2021-09-13T09:20:10] DEBUG1: new mask: 0x2000 [2021-09-13T09:20:10] DEBUG1: onKeyDown id=65533 mask=0x2000 button=0x0028 [2021-09-13T09:20:10] DEBUG1: send key down to "MAC_OS" id=65533, mask=0x2000, button=0x0028 [2021-09-13T09:20:10] DEBUG1: hook: 0x000000de 0x80280001 [2021-09-13T09:20:10] DEBUG1: hook: 0x0601e4de 0x80280001 [2021-09-13T09:20:10] DEBUG1: hook: 0x0700e4de 0x80280001 [2021-09-13T09:20:10] DEBUG1: event: Key char=228, vk=0xde, nagr=0, lParam=0x80280001 [2021-09-13T09:20:10] DEBUG1: new mask: 0x2000 [2021-09-13T09:20:10] DEBUG1: new mask: 0x2000 [2021-09-13T09:20:10] DEBUG1: onKeyUp id=65533 mask=0x2000 button=0x0028 [2021-09-13T09:20:10] DEBUG1: send key up to "MAC_OS" id=65533, mask=0x2000, button=0x0028 ``` It seems that ä gets mapped to `65533` which is https://www.fileformat.info/info/unicode/char/fffd/index.htm which maybe means that the character is not being interpreted correctly within the character encoding... (https://stackoverflow.com/questions/41462598/recieving-65533-as-char-value-for-characters-as-%C3%A0-%C3%98-%C3%A6-%C3%A6-etc) But I'm not sure about this I have not tried cloning the latest source and building it by hand on Win / Mac, maybe that helps...
Author
Owner

@matt22207 commented on GitHub (Jan 9, 2022):

I have the same issue with tilde not working:

Server: MacOS 11.6.1 w/ Barrier 2.4.0-release-3e0d758b (tried both US and US International-PC keyboard)
Client: EndeavourOS (Arch) Linux w/ Barrier 2.4.0-release-00000000

<!-- gh-comment-id:1008348317 --> @matt22207 commented on GitHub (Jan 9, 2022): I have the same issue with tilde not working: Server: MacOS 11.6.1 w/ Barrier 2.4.0-release-3e0d758b (tried both US and US International-PC keyboard) Client: EndeavourOS (Arch) Linux w/ Barrier 2.4.0-release-00000000
Author
Owner

@jroselle commented on GitHub (Apr 15, 2022):

Adding my voice - macOS as Server with latest Monterey, windows 11 client.

I was able to work around the issue by creating a Hotkey under Server config to send the tick to windows but after doing so, I lost the use of the tick in Monterey - guess I have to choose one.

<!-- gh-comment-id:1100147723 --> @jroselle commented on GitHub (Apr 15, 2022): Adding my voice - macOS as Server with latest Monterey, windows 11 client. I was able to work around the issue by creating a Hotkey under Server config to send the tick to windows but after doing so, I lost the use of the tick in Monterey - guess I have to choose one.
Author
Owner

@LuizSiqueiraNeto commented on GitHub (Apr 16, 2022):

After I reinstalled Windows, the problem disappeared.

<!-- gh-comment-id:1100645416 --> @LuizSiqueiraNeto commented on GitHub (Apr 16, 2022): After I reinstalled Windows, the problem disappeared.
Author
Owner

@rvelozo commented on GitHub (Aug 22, 2022):

I was about to say that I had the same problem and then realized that the ã will only be available in Windows if the language supports it.
I changed it to Portuguese with international keyboard. And the ã õ work as expected!

<!-- gh-comment-id:1222550616 --> @rvelozo commented on GitHub (Aug 22, 2022): I was about to say that I had the same problem and then realized that the ã will only be available in Windows if the language supports it. I changed it to Portuguese with international keyboard. And the ã õ work as expected!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#951
No description provided.