[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

Open
opened 2026-05-05 06:41:48 -06:00 by gitea-mirror · 8 comments
Owner

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

  1. On Linux (server), keyboard layout is "English (US, intl., with dead keys)"
  2. On Mac (client), the keyboard layout is "U.S. International - PC"
  3. Put the cursor on Mac
  4. Hold shift and type ' (an underlined ¨ appears)
  5. Type a space. The ¨ stays there instead of being converted to a " (double quote)

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

  • When did the problem start to occur? Since I first tried.
  • Is there a way to work around it? Yes, I must type AltGr + Shift + ' then Space to produce a "
  • Does this bug prevent you from using Barrier entirely? No

I can send debug logs if it is of any use.

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 ### 1. On Linux (server), keyboard layout is "English (US, intl., with dead keys)" 2. On Mac (client), the keyboard layout is "U.S. International - PC" 3. Put the cursor on Mac 4. Hold shift and type ' (an underlined ¨ appears) 5. Type a space. The ¨ stays there instead of being converted to a " (double quote) 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 ### * When did the problem start to occur? Since I first tried. * Is there a way to work around it? Yes, I must type AltGr + Shift + ' then Space to produce a " * Does this bug prevent you from using Barrier entirely? No I can send debug logs if it is of any use.
gitea-mirror added the
bug
label 2026-05-05 06:41:48 -06:00
Author
Owner

@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.

<!-- gh-comment-id:639159383 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:695453436 --> @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.
Author
Owner

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

Let's not close valid bug reports for no reason.

<!-- gh-comment-id:757530574 --> @p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports for no reason.
Author
Owner

@arjenveenhuizen commented on GitHub (Feb 17, 2021):

I see the exact same issue as described in the first post on this combination:

  • Server: Ubuntu 18.04 (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.
  • Client: Mac OS X Catalina 10.15.7, running barrier v2.3.3 U.S. International - PC keyboard layout.
<!-- gh-comment-id:780368130 --> @arjenveenhuizen commented on GitHub (Feb 17, 2021): I see the exact same issue as described in the first post on this combination: * Server: Ubuntu 18.04 (`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. * Client: Mac OS X Catalina 10.15.7, running barrier v2.3.3 U.S. International - PC keyboard layout.
Author
Owner

@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 client

To test eventually progress, I updated client and server to 2.4.0.

The bug still exists.

<!-- gh-comment-id:929266207 --> @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 client To test eventually progress, I updated client and server to 2.4.0. The bug still exists.
Author
Owner

@LaraArgento commented on GitHub (Sep 30, 2021):

I can't make ~ in the client, neither ". Dead Keys. us_intl layout on both.

<!-- gh-comment-id:931273480 --> @LaraArgento commented on GitHub (Sep 30, 2021): I can't make ~ in the client, neither ". Dead Keys. us_intl layout on both.
Author
Owner

@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).

<!-- gh-comment-id:946257118 --> @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).
Author
Owner

@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)

<!-- gh-comment-id:1008721337 --> @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)
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#570
No description provided.