[GH-ISSUE #260] Unable to switch to Russian layout #209

New issue

Open

opened 2026-05-05 05:41:25 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:41:25 -06:00

Owner

Originally created by @linux019 on GitHub (Feb 27, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/260

Operating Systems

Server: Ubuntu 16.0, Client - Arch (KDE)
Wayland is not used

Barrier

Server & Client version 2.1.2

I click language toggle in tray - and selected Language "RU" - my selection was ignored
Used hotkeys which are preconfigured to change layout in X - same, they are ignored. Without active Barrier all layouts work well. There are no any errors in logs even at "debug".

Any look to fix this ?

it's a part from Xorg config which describes keyboard

Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "us,ru"
        Option "XkbModel" "pc105"
        Option "XkbVariant" "qwerty"
        Option "XkbOptions" "terminate:ctrl_alt_bksp,grp:rctrl_toggle,grp:win_space_toggle"
EndSection

Originally created by @linux019 on GitHub (Feb 27, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/260 ### Operating Systems ### Server: Ubuntu 16.0, Client - Arch (KDE) Wayland is not used ### Barrier ### Server & Client version 2.1.2 1) I click language toggle in tray - and selected Language "RU" - my selection was ignored 2) Used hotkeys which are preconfigured to change layout in X - same, they are ignored. Without active Barrier all layouts work well. There are no any errors in logs even at "debug". Any look to fix this ? it's a part from Xorg config which describes keyboard ``` Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "us,ru" Option "XkbModel" "pc105" Option "XkbVariant" "qwerty" Option "XkbOptions" "terminate:ctrl_alt_bksp,grp:rctrl_toggle,grp:win_space_toggle" EndSection ```

gitea-mirror commented

2026-05-05 05:41:28 -06:00

Author

Owner

@rdewolff commented on GitHub (Mar 19, 2019):

Same issue with other international keyboard. The layout on the remote computer is ignored.

@rdewolff commented on GitHub (Mar 19, 2019): Same issue with other international keyboard. The layout on the remote computer is ignored.

gitea-mirror commented

2026-05-05 05:41:31 -06:00

Author

Owner

@rdewolff commented on GitHub (Mar 19, 2019):

That could be considered as a feature. The host choose the keyboard layout and use it.

Workaround is to change the host keyboard layout. The same layout will then be used on the remote host.

@rdewolff commented on GitHub (Mar 19, 2019): That could be considered as a feature. The host choose the keyboard layout and use it. Workaround is to change the host keyboard layout. The same layout will then be used on the remote host.

gitea-mirror commented

2026-05-05 05:41:34 -06:00

Author

Owner

@eNTi commented on GitHub (Jul 17, 2019):

This "feature" also prevents us from using anything but fallback (us) layout on a linux client machine with a windows host. I think the problem is, that the "MatchIsKeyboard" isn't working with a "virtual" device? The easiest workaround could be some kind of "command on switch" that will let us run setxkbmap to switch the layout?

@eNTi commented on GitHub (Jul 17, 2019): This "feature" also prevents us from using anything but fallback (us) layout on a linux client machine with a windows host. I think the problem is, that the "MatchIsKeyboard" isn't working with a "virtual" device? The easiest workaround could be some kind of "command on switch" that will let us run setxkbmap to switch the layout?

gitea-mirror commented

2026-05-05 05:41:37 -06:00

Author

Owner

@darkdragon-001 commented on GitHub (Dec 20, 2020):

See meta issue #45.

@darkdragon-001 commented on GitHub (Dec 20, 2020): See meta issue #45.