github-starred/barrier

Fork 0

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

[GH-ISSUE #1143] Some accent dead keys don't work on client with Brazilian (ABNT) keyboard #916

New issue

Open

opened 2026-05-05 07:16:43 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 07:16:43 -06:00

Owner

Originally created by @ekalin on GitHub (Apr 22, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1143

Describe the bug
Some accented characters are not output on the client.

Server and client have their keyboards set to Brazilian (ABNT) layout. That's the standard layout for Brazil. Sometimes it's called ABNT2.

When the focus is in the client, pressing ^+e outputs just e, instead of ê. Same for other combinations. Pressing ^ twice, which should output ^, also does not work. It seems the ^ dead key is just not sent or recognized. In the server it works, and it also works with a keyboard locally connected to the client.

The same happens with the combining grave accent `.

However, the acute accent ´ and the tilde ~ work as expected.

To Reproduce
Steps to reproduce the behavior:

Set layout on server to Brazilian (ABNT) (might be displayed as ABNT2). This is the layout: http://kbdlayout.info/KBDBR/. I'm not sure if the layout on the client is relevant.
With focus on the client, press ^ (on a US layout, that would be the '/" key, with SHIFT) and 'e'. Instead of 'ê' only 'e' is output. (Or ô, â, etc.)
For the grave accent, press ` (on a US layout, the [/{ key, with SHIFT) and 'a', and only 'a' is output instead of à. (Also for ò, ù, etc).

Expected behavior
The accented character should be output.

Desktop (please complete the following information):
Server: Linux, 2.3.3
Client: Windows 10, 2.3.3

Additional context
I can provide more info and logs, but I'm not sure what's useful or relevant, so please describe how to collect more information.

Originally created by @ekalin on GitHub (Apr 22, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1143 **Describe the bug** Some accented characters are not output on the client. Server and client have their keyboards set to Brazilian (ABNT) layout. That's the standard layout for Brazil. Sometimes it's called ABNT2. When the focus is in the client, pressing ^+e outputs just e, instead of ê. Same for other combinations. Pressing ^ twice, which should output ^, also does not work. It seems the ^ dead key is just not sent or recognized. In the server it works, and it also works with a keyboard locally connected to the client. The same happens with the combining grave accent `. However, the acute accent ´ and the tilde ~ work as expected. **To Reproduce** Steps to reproduce the behavior: 1. Set layout on server to Brazilian (ABNT) (might be displayed as ABNT2). This is the layout: http://kbdlayout.info/KBDBR/. I'm not sure if the layout on the client is relevant. 2. With focus on the client, press ^ (on a US layout, that would be the '/" key, with SHIFT) and 'e'. Instead of 'ê' only 'e' is output. (Or ô, â, etc.) 3. For the grave accent, press ` (on a US layout, the [/{ key, with SHIFT) and 'a', and only 'a' is output instead of à. (Also for ò, ù, etc). **Expected behavior** The accented character should be output. **Desktop (please complete the following information):** Server: Linux, 2.3.3 Client: Windows 10, 2.3.3 **Additional context** I can provide more info and logs, but I'm not sure what's useful or relevant, so please describe how to collect more information.

gitea-mirror commented

2026-05-05 07:16:46 -06:00

Author

Owner

@gabaweb commented on GitHub (May 18, 2021):

I have the same problem, but my server and client are Windows 10.

I can't create some special characters with the Brazilian Portuguese keyboard on the client machine, for exemple: ê (Shift + ~ + e) and à (Shift + ´ + a).

Others that don't require Shift to be pressed are working fine, for exemple: é (´ + e) or ã (~ + a).

Both machines are set to the Brazilian Portuguese keyboard and using Windows 10.

@gabaweb commented on GitHub (May 18, 2021): I have the same problem, but my server and client are Windows 10. I can't create some special characters with the Brazilian Portuguese keyboard on the client machine, for exemple: ê (Shift + ~ + e) and à (Shift + ´ + a). Others that don't require Shift to be pressed are working fine, for exemple: é (´ + e) or ã (~ + a). Both machines are set to the Brazilian Portuguese keyboard and using Windows 10.

gitea-mirror commented

2026-05-05 07:16:48 -06:00

Author

Owner

@lucas2595 commented on GitHub (May 24, 2021):

Both my machines are Ubuntu 18.04 with barrier 2.3.3 and the accents work just fine for me. So to whoever looks into it, this might be platform specific.

@lucas2595 commented on GitHub (May 24, 2021): Both my machines are Ubuntu 18.04 with barrier 2.3.3 and the accents work just fine for me. So to whoever looks into it, this might be platform specific.

gitea-mirror commented

2026-05-05 07:16:49 -06:00

Author

Owner

@pv2b commented on GitHub (Dec 19, 2021):

I am running into the same issue on a Swedish keyboard. Accents that require a shift key will not work.

The barrier server is running 2.4.0 on Windows 11, the barrier client is running 2.3.6 on Windows 10.

@pv2b commented on GitHub (Dec 19, 2021): I am running into the same issue on a Swedish keyboard. Accents that require a shift key will not work. The barrier server is running 2.4.0 on Windows 11, the barrier client is running 2.3.6 on Windows 10.

gitea-mirror commented

2026-05-05 07:16:51 -06:00

Author

Owner

@dnlm commented on GitHub (Feb 15, 2022):

I guess I've got the same issue on a German keyboard, the grave accent ( ` ) requires the shift key (plus accent ´ ) and does not work on the client. So I guess this is not limited to the Brazilian keyboard.

Client and Server are both barrier 2.3.3 running on Windows 10.

@dnlm commented on GitHub (Feb 15, 2022): I guess I've got the same issue on a German keyboard, the grave accent ( ` ) requires the shift key (plus accent ´ ) and does not work on the client. So I guess this is not limited to the Brazilian keyboard. Client and Server are both barrier 2.3.3 running on Windows 10.

gitea-mirror commented

2026-05-05 07:16:52 -06:00

Author

Owner

@rgr-prog commented on GitHub (Jun 3, 2022):

I have the same issue using shit+~+a (ã) or any accent that uses shift. My server is a MacOSx and the client a Windows 10.

@rgr-prog commented on GitHub (Jun 3, 2022): I have the same issue using shit+~+a (ã) or any accent that uses shift. My server is a MacOSx and the client a Windows 10.

gitea-mirror commented

2026-05-05 07:16:54 -06:00

Author

Owner

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

Running client on OSX and server on Windows 10
v 2.3.3-release-3395cca9

I am able to get áéíóúç but not
`a (expected) à
~a (expected) ã

@rvelozo commented on GitHub (Aug 22, 2022): Running client on OSX and server on Windows 10 v 2.3.3-release-3395cca9 I am able to get áéíóúç but not `a (expected) à ~a (expected) ã

gitea-mirror commented

2026-05-05 07:16:55 -06:00

Author

Owner

@natanaugusto commented on GitHub (May 4, 2023):

I have the same problem and I resolved that after reading this issue #134.

I just added this line on my .bashrc:

setxkbmap -device 5 br

I hope that helps.

@natanaugusto commented on GitHub (May 4, 2023): I have the same problem and I resolved that after reading this issue [#134](https://github.com/debauchee/barrier/issues/134). I just added this line on my `.bashrc`: ``` setxkbmap -device 5 br ``` I hope that helps.