github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #465] AltGr related characters don't work in WSL or X2Go client #362

New issue

Open

opened 2026-05-05 06:07:45 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

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

Owner

Originally created by @ktuulos on GitHub (Oct 16, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/465

Details

Operating Systems

Server: Ubuntu 18.04, kernel 4.15.0-65-generic
Client: Windows 10 Enterprise, Version 1903 (OS Build 18362.418)

Barrier Version

Server: Barrier Linux client, version 2.32-snapshot-210c2b70, installed from flatpak
Client: Barrier Windows client, version 2.3.2-snapshot-210c2b70

Steps to reproduce bug

I'm using Finnish keyboard. This means, that some characters (e.g. @£$€) are composed using the AltGr-key. These characters work fine on other Windows applications (like MS Word, Outlook, Command prompt, Chrome), but they don't work with "Windows subsystem for Linux / Ubuntu 18.04" or "X2Go client v4.1.2.0 Qt 4.8.6". On these, AltGr-composed keys function, as I would have pressed Ctrl and the key.

I assume, that if the Barrier client behaviour could be fixed for WSL, then also X2Go client would work.

Other info

Here is my config file for server:

---8<---8<---
section: screens
        MYWINDOWS:
                halfDuplexCapsLock = false
                halfDuplexNumLock = false
                halfDuplexScrollLock = false
                xtestIsXineramaUnaware = false
                preserveFocus = false
                switchCorners = none 
                switchCornerSize = 0
                meta = altgr
                altgr = shift
        my-linux:
                halfDuplexCapsLock = false
                halfDuplexNumLock = false
                halfDuplexScrollLock = false
                xtestIsXineramaUnaware = false
                preserveFocus = false
                switchCorners = none 
                switchCornerSize = 0
end

section: aliases
end

section: links
        MYWINDOWS:
                right = my-linux
        my-linux:
                left = MYWINDOWS
end

section: options
        heartbeat = 5000
        relativeMouseMoves = false
        screenSaverSync = true
        win32KeepForeground = false
        clipboardSharing = true
        switchCorners = none 
        switchCornerSize = 0
end
---8<---8<---

Here is my config file for client:
---8<---8<---
section: screens
end

section: aliases
end


section: links
end

section: options
	relativeMouseMoves = false
	screenSaverSync = true
	win32KeepForeground = false
	clipboardSharing = true
	switchCorners = none 
	switchCornerSize = 0
end
---8<---8<---

Originally created by @ktuulos on GitHub (Oct 16, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/465 <details> <summary>Details</summary> </details> ### Operating Systems ### Server: Ubuntu 18.04, kernel 4.15.0-65-generic Client: Windows 10 Enterprise, Version 1903 (OS Build 18362.418) ### Barrier Version ### Server: Barrier Linux client, version 2.32-snapshot-210c2b70, installed from flatpak Client: Barrier Windows client, version 2.3.2-snapshot-210c2b70 ### Steps to reproduce bug ### I'm using Finnish keyboard. This means, that some characters (e.g. @£$€) are composed using the AltGr-key. These characters work fine on other Windows applications (like MS Word, Outlook, Command prompt, Chrome), but they don't work with "Windows subsystem for Linux / Ubuntu 18.04" or "X2Go client v4.1.2.0 Qt 4.8.6". On these, AltGr-composed keys function, as I would have pressed Ctrl and the key. I assume, that if the Barrier client behaviour could be fixed for WSL, then also X2Go client would work. ### Other info ### Here is my config file for server: ``` ---8<---8<--- section: screens MYWINDOWS: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false preserveFocus = false switchCorners = none switchCornerSize = 0 meta = altgr altgr = shift my-linux: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false preserveFocus = false switchCorners = none switchCornerSize = 0 end section: aliases end section: links MYWINDOWS: right = my-linux my-linux: left = MYWINDOWS end section: options heartbeat = 5000 relativeMouseMoves = false screenSaverSync = true win32KeepForeground = false clipboardSharing = true switchCorners = none switchCornerSize = 0 end ---8<---8<--- Here is my config file for client: ---8<---8<--- section: screens end section: aliases end section: links end section: options relativeMouseMoves = false screenSaverSync = true win32KeepForeground = false clipboardSharing = true switchCorners = none switchCornerSize = 0 end ---8<---8<--- ```

gitea-mirror added the

bug

label 2026-05-05 06:07:45 -06:00

gitea-mirror commented

2026-05-05 06:07:49 -06:00

Author

Owner

@ktuulos commented on GitHub (Oct 17, 2019):

Additional information: The problem concerns also OneNote 2016. On that, AltGr characters don't behave as Ctrl characters, but they behave otherwise strange. E.g. AltGr-4, which is supposed to produce $ character, changes style to Heading 2.

@ktuulos commented on GitHub (Oct 17, 2019): Additional information: The problem concerns also OneNote 2016. On that, AltGr characters don't behave as Ctrl characters, but they behave otherwise strange. E.g. AltGr-4, which is supposed to produce $ character, changes style to Heading 2.

gitea-mirror commented

2026-05-05 06:07:53 -06:00

Author

Owner

@koodzi commented on GitHub (Oct 17, 2019):

It seems like I have the same problem, but with Polish diacritic letters.

To create accented letters we use a combination of [left alt] and [letter]
Alt + one of "acelnoszx" should give "ąćęłnóśźż"

I tired combination of languages on both systems:

Server	Client	Sample	Result
PL	PL	"Zażółć gęślą jaźń"	"za g ja" (missing accented letters)
PL	EN	"Zażółć gęślą jaźń"	"za g ja"
EN	PL	"Zażółć gęślą jaźń"	"zazolc gesla jazn"
EN	EN	"Zażółć gęślą jaźń"	"zazolc gesla jazn"

Operating Systems
Server: Ubuntu 18.04
Client: Windows 10 Enterprise

Barrier Version
Server: Barrier Linux client, version 2.32-snapshot-6daa516e, build date: Oct 16 2019, installed from snap
Client: Barrier Windows client, version 2.3.2-snapshot-58d8f020, build date: 9 Aug 2019, installed from choco

@koodzi commented on GitHub (Oct 17, 2019): It seems like I have the same problem, but with Polish diacritic letters. To create accented letters we use a combination of [left alt] and [letter] Alt + one of "acelnoszx" should give "ąćęłnóśźż" I tired combination of languages on both systems: | Server | Client | Sample | Result | | --- | --- | --- | --- | | PL| PL | "Zażółć gęślą jaźń" | "za g ja" (missing accented letters) | | PL | EN | "Zażółć gęślą jaźń" | "za g ja" | | EN | PL | "Zażółć gęślą jaźń" | "zazolc gesla jazn" | | EN | EN | "Zażółć gęślą jaźń" | "zazolc gesla jazn" | **Operating Systems** Server: Ubuntu 18.04 Client: Windows 10 Enterprise **Barrier Version** Server: Barrier Linux client, version 2.32-snapshot-6daa516e, build date: Oct 16 2019, installed from snap Client: Barrier Windows client, version 2.3.2-snapshot-58d8f020, build date: 9 Aug 2019, installed from choco

gitea-mirror commented

2026-05-05 06:07:55 -06:00

Author

Owner

@andrei-pavel commented on GitHub (Dec 3, 2019):

Same problem for Romanian

Operating Systems

Server: Windows 10 1903 (OS build 18362.476)
Client: ArchLinux with kernel 5.4.1

Barrier Version

Server: 2.3.2-snapshot-210c2b70
Client: 2.3.2-RELEASE-00000000

Steps to reproduce bug

On the client, choose Romanian keyboard language (label ro) or any other language that has diacritics or special characters that are typed by pressing alt + <letter>.
Press alt + [QqTtIiAaSs].
It should show ÂâȚțÎîĂăȘș, it shows Ââ??ÎîAa??. Only 4 out of 10 work. Pressing the combinations on the local keyboard works for all 10.

Any idea why?

@andrei-pavel commented on GitHub (Dec 3, 2019): Same problem for Romanian ### Operating Systems ### Server: Windows 10 1903 (OS build 18362.476) Client: ArchLinux with kernel 5.4.1 ### Barrier Version ### Server: 2.3.2-snapshot-210c2b70 Client: 2.3.2-RELEASE-00000000 ### Steps to reproduce bug ### 1. On the client, choose Romanian keyboard language (label `ro`) or any other language that has diacritics or special characters that are typed by pressing `alt + <letter>`. 2. Press `alt + [QqTtIiAaSs]`. 3. It should show `ÂâȚțÎîĂăȘș`, it shows `Ââ??ÎîAa??`. Only 4 out of 10 work. Pressing the combinations on the local keyboard works for all 10. Any idea why?

gitea-mirror commented

2026-05-05 06:07:58 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 1, 2020):

Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

@github-actions[bot] commented on GitHub (Oct 1, 2020): Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

gitea-mirror commented

2026-05-05 06:07:59 -06:00

Author

Owner

@ktuulos commented on GitHub (Oct 19, 2020):

This problem exists still.
Windows version 2.3.3-release-3395cca9
Ubuntu 18.04 LTS snap version 2.3.3-release-bbd1accb

@ktuulos commented on GitHub (Oct 19, 2020): This problem exists still. Windows version 2.3.3-release-3395cca9 Ubuntu 18.04 LTS snap version 2.3.3-release-bbd1accb

gitea-mirror referenced this issue

2026-05-05 06:39:05 -06:00

[GH-ISSUE #686] Linux server segmentation fault #546

gitea-mirror referenced this issue

2026-05-05 06:39:23 -06:00

[GH-ISSUE #686] Linux server segmentation fault #546