[GH-ISSUE #693] ABNT Keyboard failure (Brazilian) #552

New issue

Open

opened 2026-05-05 06:39:55 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:39:55 -06:00

Owner

Originally created by @brzuck on GitHub (May 25, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/693

Operating Systems

Server: Windows 10 Pro (Version 1909)

Barrier Version

2.3.2-snapshot

Steps to reproduce bug / Other info

Installed Barrier and used normally with my client (client OS not important as I will describe)
Over the next few days I started to notice that my keyboard was failing to write for example this string: "ção" which is a combination for strokes ç + ~ + a + o
And an impotant note: I didn't use Barrier anymore those days! I didn't have Barrier open and running in my taskboard.
I was already in contact with my keyboard seller, because I have bought it just a couple weeks ago and I thought it was failing.
Started to make a few more tests to try to figure it out and I saw that there was a process from barrier still running on my computer and when I finished that process, the keyboard started to work again.
It was failing when I was pressing at normal typing speed. If I press slow, it works.
Some more examples - pé: pe / çã: ça / çõ: ço

Originally created by @brzuck on GitHub (May 25, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/693 ### Operating Systems ### Server: Windows 10 Pro (Version 1909) ### Barrier Version ### 2.3.2-snapshot ### Steps to reproduce bug / Other info ### - Installed Barrier and used normally with my client (client OS not important as I will describe) - Over the next few days I started to notice that my keyboard was failing to write for example this string: "ção" which is a combination for strokes **ç** + **~** + **a** + **o** - And an impotant note: I didn't use Barrier anymore those days! I didn't have Barrier open and running in my taskboard. - I was already in contact with my keyboard seller, because I have bought it just a couple weeks ago and I thought it was failing. - Started to make a few more tests to try to figure it out and I saw that there was a process from barrier still running on my computer and when I finished that process, the keyboard started to work again. - It was failing when I was pressing at normal typing speed. If I press slow, it works. - Some more examples - pé: pe / çã: ça / çõ: ço

gitea-mirror added the

bug

label 2026-05-05 06:39:55 -06:00

gitea-mirror commented

2026-05-05 06:39:58 -06:00

Author

Owner

@brzuck commented on GitHub (Jun 5, 2020):

Video: https://www.dropbox.com/s/0vfjnvpcyvftde4/Untitled.mp4?dl=0

@brzuck commented on GitHub (Jun 5, 2020): Video: https://www.dropbox.com/s/0vfjnvpcyvftde4/Untitled.mp4?dl=0

gitea-mirror commented

2026-05-05 06:40:00 -06:00

Author

Owner

@eliezerriani commented on GitHub (Jun 25, 2020):

Hi @brzuck k, this occurs with me too.
And one more thing that can be related: I can't type letters with the "^" at client computers (in the server works), e.g. "â" and "ô".
The "^" is not posed on the char.
But the char "^" is printed if I type "^" + space.

@eliezerriani commented on GitHub (Jun 25, 2020): Hi @brzuck k, this occurs with me too. And one more thing that can be related: I can't type letters with the "^" at client computers (in the server works), e.g. "â" and "ô". The "^" is not posed on the char. But the char "^" is printed if I type "^" + space.

gitea-mirror commented

2026-05-05 06:40:02 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 21, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 21, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:40:06 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Let's not close valid bug reports.

@p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports.