mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1160] Accent marks not working properly #933
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#933
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 @nicomagalhaes on GitHub (May 10, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1160
I'm using Barrier to integrate a PC and a laptop (PC as server), and several times the accent marks do not work properly. Sometimes, they do not appear, and sometimes they appear twice.
Steps to reproduce the behavior:
nao está funcionando
nao está funcionando
não esta funcionando
não esta funcionando
não está funcionando
nãõ est´a funcionando
nãõ est´á funcionando
nao est´á funcionando
nãõ est´á funcionando
nao est´á funcionando
The sentence should be the following on both Server and Client:
não está funcionando
Desktop (please complete the following information):
Additional context
I'm using the keyboard on the server connected by a USB cable.
@alpcastro commented on GitHub (May 19, 2021):
These accents works for me ! My problem is with circunflex accent (^). Like in â ê î ô û. It works OK on my server machine (Linux Ubuntu), but only the voguel a e i o u appears on the client Windows 10.
Is there a config file to recode the keys while transmitting ?
@janevert commented on GitHub (Jun 2, 2021):
Same issue here, using barrier server on Ubuntu (21.04) and client on Win10. Both barrier are version 2.3.3.
For me, the affected letters are ' " ~ (single quote, double quote and tilde).
Perhaps this has something to do that in windows these are combined letters? In windows, I have to press "single quote" and then "space" to produce a single quote symbol. Same for the double quote and tilde.
When doing this sequence from the barrier server, the single quote is not produced, but a space character.
Note that switching windows to a language which doesn't use combined letters, English for example, then this issue doesn't show. And the three letters I mentioned work as expected.
So I have to add that my windows is set to Dutch language by default which uses these combined letters.
@LaraArgento commented on GitHub (Nov 3, 2021):
same here. I have to Reload Barrier in order to fix the issue, but it comes back in a matter of a few minutes and it is very annoying.
@stephen-neumeyer commented on GitHub (Feb 18, 2022):
tilde (~) does not work across barrier (on client system). server: mac osx 'monterey' client: ubuntu 20.04.3 LTS. i turned off SSL on client & server. i'm using mostly default options, on the client side, i manually entered the server's ip address. (i'm inside a subnet for both systems).
@abastola0 commented on GitHub (Mar 10, 2022):
You can Map the ~ and ` to themselves again in the hotkeys section. Worked for me !!
@bobstro commented on GitHub (Jun 21, 2022):
Mapping in server settings will send the correct keys to the client, but if you press them with focus on the server, the keys are sent to the client and not usable on the server.
@felipe-vf commented on GitHub (Jul 8, 2022):
Could you provide a screenshot of how the configuration looks like? I tried mapping the hotkeys but the problem still persists on the client side. Both computers are running Windows.
@abastola0 commented on GitHub (Jul 11, 2022):
Create a hotkey and select the action for the same. In this case tilde or any other keys that don't work on the client. Remember this way works only for the client. For example: if you set tilde this way, the tilde would work on the client but on on the server. See image attached !

@abastola0 commented on GitHub (Jul 11, 2022):
yeah is there any possible solution to it apart from setting up the hotkey?