mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #727] On US Intl Keyboard (dead keys), shift + single quote then Space produces diaeresis (U+00A8) on the client instead of quotation mark (U+00A8) #570
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#570
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 @efibe on GitHub (Jun 1, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/727
Operating Systems
Server: Barrier 2.3.1 on Linux (Ubuntu 19.10)
Client: Barrier 2.3.2 on MacOS Catalina 10.5.15
Barrier Version
2.3.1 (server), 2.3.2 (client)
Steps to reproduce bug
The expected behavior is either the underlined ¨ being converted to a " after hitting the space bar on step 5, or the underlined " appearing right away on step 4.
If I use this combo on the server, the underlined ¨ appears first, but when I type the space, it's converted to a " correctly.
On the physical Mac keyboard, this combo produces an underlined " initially, which stays there after a space bar.
On all cases and keyboards, if I use a vowel instead of the space bar, I get ä ë ï ö ü, which is the expected behavior.
Other info
I can send debug logs if it is of any use.
@krizalidzero commented on GitHub (Jun 4, 2020):
I have Windows 10 and Windows 10, both systems set to Japanese and both systems with Spanish and Japanese keyboard layouts enabled.
Dead keys do not work for me at all via barrier.
@github-actions[bot] commented on GitHub (Sep 20, 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.
@p12tic commented on GitHub (Jan 10, 2021):
Let's not close valid bug reports for no reason.
@arjenveenhuizen commented on GitHub (Feb 17, 2021):
I see the exact same issue as described in the first post on this combination:
Linux 5.7.1-050701-generic #202006071230 SMP Sun Jun 7 12:32:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux), running barrier v2.3.3 and English US Intl. with deadkeys keyboard layout.@ascheucher commented on GitHub (Sep 28, 2021):
I have a Mac OS Big Sur Server and Client with US International Keyboard on both.
Both with Barrier 2.3.3-release-3395cca9
My problems are
'require typing "+SPACE, which produces≠on the client"require typing '+SPACE or "+SPACE, which produces@in the clientTo test eventually progress, I updated client and server to 2.4.0.
The bug still exists.
@LaraArgento commented on GitHub (Sep 30, 2021):
I can't make ~ in the client, neither ". Dead Keys. us_intl layout on both.
@null-von-sushi commented on GitHub (Oct 19, 2021):
I am also having issues, but I cannot really describe it because the behaviour is a bit random. The most common issue I had though is that (on an ANSI keyboard) typing single quote or double quote, will switch to another keyboard layout.
My server is Windows 10 (86_64), my current clients are Windows 11 (x86_64 and aarch64).
@elegos commented on GitHub (Jan 10, 2022):
Here I have what I think the same problem:
Key requiring [Key], [Space] are ignored (simple space is sent) (examples: " (SHIFT + ', SPACE), ~ (SHIFT+`, SPACE)).
EDIT: some combinations are not ignored, like ' or ` (that are [KEY] + SPACE)
Host: Linux (Fedora) w/ barrier 2.3.3, keyboard layout: US (international)
Guest: Windows w/ barrier 2.4.0, keyboard layout: US (international)