[GH-ISSUE #638] Wrong keyboard layout between Server and Client #505

Open
opened 2026-05-05 06:33:20 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @pierremouvet on GitHub (Apr 25, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/638

Operating Systems

Server Debian Buster 10.3.0
Client Raspbian Buster

Barrier Version

2.3.2

On debian I use a french keyboard.
On raspbian I use a french keyboard.
Both work fine.
When switching from debain to raspbian in barrier, I still have a french keyboad but no franch keys like éàç ...

When in client (raspbian) if I launch a remote desktop to windows 7-8-10-2012-2016 (remmina) I have a qwerty keyboard.

When in client (raspbian) if I launch a remote desktop to windows 2003 (remmina) I can't type anything

I check with
setxkbmap -query
rules: evdev
model: pc105
layout: be
Both layout are OK

On the server (debian) with same configuration and using remmina everything works perfectly.

Steps to reproduce bug

just install and run

Other info

  • When did the problem start to occur? At fresh install
  • Is there a way to work around it? No.
  • Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

Thanks a lot for your help.

Originally created by @pierremouvet on GitHub (Apr 25, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/638 ### Operating Systems ### Server Debian Buster 10.3.0 Client Raspbian Buster ### Barrier Version ### 2.3.2 On debian I use a french keyboard. On raspbian I use a french keyboard. Both work fine. When switching from debain to raspbian in barrier, I still have a french keyboad but no franch keys like éàç ... When in client (raspbian) if I launch a remote desktop to windows 7-8-10-2012-2016 (remmina) I have a qwerty keyboard. When in client (raspbian) if I launch a remote desktop to windows 2003 (remmina) I can't type anything I check with setxkbmap -query rules: evdev model: pc105 layout: be Both layout are OK On the server (debian) with same configuration and using remmina everything works perfectly. ### Steps to reproduce bug ### just install and run ### Other info ### * When did the problem start to occur? At fresh install * Is there a way to work around it? No. * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here. Thanks a lot for your help.
Author
Owner

@whythefyouflying commented on GitHub (Apr 26, 2020):

I have the same issue on my end with Windows 10 and Ubuntu 20.04 LTS. Both have a Polish keyboard layout, the Windows 10 box is the server and the Ubuntu is the client. Barrier works, however it seems like it works only in pseudo-ASCII way. The special Polish characters like: ąęłćźż don't work, funnily enough, only one character works which is: ó.

<!-- gh-comment-id:619601669 --> @whythefyouflying commented on GitHub (Apr 26, 2020): I have the same issue on my end with Windows 10 and Ubuntu 20.04 LTS. Both have a Polish keyboard layout, the Windows 10 box is the server and the Ubuntu is the client. Barrier works, however it seems like it works only in pseudo-ASCII way. The special Polish characters like: ąęłćźż don't work, funnily enough, only one character works which is: ó.
Author
Owner

@metalgrid commented on GitHub (Apr 28, 2020):

Windows 10 Pro server, Windows 10 Home client with US/BG layouts. Switching the layout on the client appears to work ( the language bar changes ) but inputs are still US. Switching to BG on server produces only question marks on the client, with no regards to the client's selected layout.

<!-- gh-comment-id:620858436 --> @metalgrid commented on GitHub (Apr 28, 2020): Windows 10 Pro server, Windows 10 Home client with US/BG layouts. Switching the layout on the client appears to work ( the language bar changes ) but inputs are still US. Switching to BG on server produces only question marks on the client, with no regards to the client's selected layout.
Author
Owner

@josschm commented on GitHub (May 5, 2020):

I have a Manjaro server and a dualboot client (Windwos/Ubuntu). All settings using DE-keyboard. But when typing on the server, the keyboard on the client seems to be US keyboard.

<!-- gh-comment-id:624031232 --> @josschm commented on GitHub (May 5, 2020): I have a Manjaro server and a dualboot client (Windwos/Ubuntu). All settings using DE-keyboard. But when typing on the server, the keyboard on the client seems to be US keyboard.
Author
Owner

@ThorstenWirth commented on GitHub (May 22, 2020):

Workaround: https://github.com/debauchee/barrier/issues/134

i've used

setxkbmap -device `xinput list | grep "Virtual core XTEST keyboard" | sed -e 's/.\+=\([0-9]\+\).\+/\1/'` de

Now it works fine

<!-- gh-comment-id:632928012 --> @ThorstenWirth commented on GitHub (May 22, 2020): Workaround: https://github.com/debauchee/barrier/issues/134 i've used ``` setxkbmap -device `xinput list | grep "Virtual core XTEST keyboard" | sed -e 's/.\+=\([0-9]\+\).\+/\1/'` de ``` Now it works fine
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 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:697070256 --> @github-actions[bot] commented on GitHub (Sep 23, 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

@pierremouvet commented on GitHub (Sep 23, 2020):

Don't close because it's not yet solved.
Can the programer deal with this issue ?
Thanks a lot.

<!-- gh-comment-id:697159013 --> @pierremouvet commented on GitHub (Sep 23, 2020): Don't close because it's not yet solved. Can the programer deal with this issue ? Thanks a lot.
Author
Owner

@eugenegff commented on GitHub (Oct 14, 2020):

Problems when Barrier server is on Windows - solved by pull request https://github.com/debauchee/barrier/pull/910

<!-- gh-comment-id:708590390 --> @eugenegff commented on GitHub (Oct 14, 2020): Problems when Barrier server is on Windows - solved by pull request https://github.com/debauchee/barrier/pull/910
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#505
No description provided.