[GH-ISSUE #764] Macbook client always uses US keyboard layout #598

New issue

Open

opened 2026-05-05 06:44:56 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:44:56 -06:00

Owner

Originally created by @simonporter007 on GitHub (Jun 23, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/764

Operating Systems

Server: Debian 10

Client: Macbook Pro Catalina 10.15.5

Barrier Version

Server: 2.2.0
Client: 2.3.2

Steps to reproduce bug

Setup debian server using GB keyboard layout
Connected MacBook client (input source also set to GB keyboard layout)
Type with keyboard focused on Macbook client results in US layout
Disconnect Barrier, typing on mac keyboard results in GB layout

Other info

I found similar issues though they all reference Linux as the client, and use a workaround to force the keyboard layout over CLI. I've tried this in case it worked, though I think the issue is Mac being the client in this case.

Originally created by @simonporter007 on GitHub (Jun 23, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/764 ### Operating Systems ### Server: Debian 10 Client: Macbook Pro Catalina 10.15.5 ### Barrier Version ### Server: 2.2.0 Client: 2.3.2 ### Steps to reproduce bug ### 1. Setup debian server using GB keyboard layout 2. Connected MacBook client (input source also set to GB keyboard layout) 3. Type with keyboard focused on Macbook client results in US layout 4. Disconnect Barrier, typing on mac keyboard results in GB layout ### Other info ### I found similar issues though they all reference Linux as the client, and use a workaround to force the keyboard layout over CLI. I've tried this in case it worked, though I think the issue is Mac being the client in this case.

gitea-mirror commented

2026-05-05 06:45:00 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 19, 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 19, 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:45:02 -06:00

Author

Owner

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

Let's not close valid bugs without a valid reason.

@p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bugs without a valid reason.