github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 22:01:23 -06:00

[GH-ISSUE #186] Problems with Neo2 layout #149

New issue

Open

opened 2026-05-05 05:24:03 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 05:24:03 -06:00

Owner

Originally created by @ghost on GitHub (Nov 30, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/186

Operating Systems

Server: Arch Linux

Client: Windows 10

Barrier Version

2.1.0

Steps to reproduce bug

Use Neo2 keyboard layout on the host
start pressing capslock and a for example or AltGr and i.
You will see that instead of writing "{" or moving the text cursor 1 to the left you will see nothing. Also in these layers, the letter positioning gets scrambled...

Other info

When did the problem start to occur? Always
Is there a way to work around it? No, not one that I know of.
Does this bug prevent you from using Barrier entirely? No

https://neo-layout.org/

Originally created by @ghost on GitHub (Nov 30, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/186 ### Operating Systems ### Server: Arch Linux Client: Windows 10 ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1. Use Neo2 keyboard layout on the host 2. start pressing capslock and a for example or AltGr and i. 3. You will see that instead of writing "{" or moving the text cursor 1 to the left you will see nothing. Also in these layers, the letter positioning gets scrambled... ### Other info ### * When did the problem start to occur? Always * Is there a way to work around it? No, not one that I know of. * Does this bug prevent you from using Barrier entirely? No https://neo-layout.org/

gitea-mirror added the

bug

label 2026-05-05 05:24:03 -06:00

gitea-mirror commented

2026-05-05 05:24:07 -06:00

Author

Owner

@Mayerch1 commented on GitHub (Jan 16, 2019):

Can confirm that on a ubuntu (server) to windows (client) configuration.
The layout is set on both machine (using kbdneo on windows), but Layers 3-6 are not working.

I also noticed that, if you got the qwertz/y layout as secondary, your windows machine will switch to that as soon as you hit the first advanced layer.
Linux to Linux is working with Neo2 (when steps provided by #134 are followed on the client computer).

So it seems to be an issue with the neo2 driver but I cannot verify that on a "Windows -> Linux" configuration with my current setup.

I'd keep the issue opened until someone can verify the same driver-caused behavior on a "windows (server) to linux (client)" configuration.
But I think it's safe to tag it with 'Windows'

@Mayerch1 commented on GitHub (Jan 16, 2019): Can confirm that on a ubuntu (server) to windows (client) configuration. The layout is set on both machine (using kbdneo on windows), but Layers 3-6 are not working. I also noticed that, if you got the qwertz/y layout as secondary, your windows machine will switch to that as soon as you hit the first advanced layer. Linux to Linux is working with Neo2 (when steps provided by #134 are followed on the client computer). So it seems to be an issue with the neo2 driver but I cannot verify that on a "Windows -> Linux" configuration with my current setup. I'd keep the issue opened until someone can verify the same driver-caused behavior on a "windows (server) to linux (client)" configuration. But I think it's safe to tag it with 'Windows'

gitea-mirror commented

2026-05-05 05:24:09 -06:00

Author

Owner

@Mayerch1 commented on GitHub (Jan 18, 2019):

I finally tested it on a "Windows (Server) -> Ubuntu (Client)" Configuration and everything works great after changing the layout of the Virtual core XTEST keyboard.

It seems to be a problem with the Windows machine (either the equivalent to Virtual core XTEST or with the neo driver). Maybe you can find a hint in their forums.

@Mayerch1 commented on GitHub (Jan 18, 2019): I finally tested it on a "Windows (Server) -> Ubuntu (Client)" Configuration and everything works great after changing the layout of the ```Virtual core XTEST keyboard```. It seems to be a problem with the Windows machine (either the equivalent to Virtual core XTEST or with the neo driver). Maybe you can find a hint in their forums.

gitea-mirror commented

2026-05-05 05:24:12 -06:00

Author

Owner

@ghost commented on GitHub (Jan 18, 2019):

I think ill report an issue at wiki.neo-layout.org and see what happens :)

@ghost commented on GitHub (Jan 18, 2019): I think ill report an issue at wiki.neo-layout.org and see what happens :)

gitea-mirror commented

2026-05-05 05:24:14 -06:00

Author

Owner

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

I'd like to get back on this, since it doesn't seem to be solved yet. Besides I'm not sure this issue is caused by the Windows driver. I have the same issue with Win10 (server) and Manjaro (client). As described above, the client is not interpreting Capslock as Mod3. The right sided Mod3 works fine however.

This doesn't only occur on kbdneo driver, but also on neo-llkh, the low-level keyboard hook driver. Since both drivers result in exactly the same behaviour on the client, I expect the problem rather on Barrier side. Directly plugged keyboards work as intended on either system.

On the linux client, xev -event keyboard doesn't recognize anything when capslock is pressed. but the capslock LED lights up on the keyboard. As long as I don't press it again, all characters except letters (!) are caps locked: numbers and punctuation characters.

I don't fully understand what Mayerch1 means with

Configuration and everything works great after changing the layout of the Virtual core XTEST keyboard.

Experimenting a bit with that did not make any change to the capslock behaviour.

@clundomac commented on GitHub (May 5, 2020): I'd like to get back on this, since it doesn't seem to be solved yet. Besides I'm not sure this issue is caused by the Windows driver. I have the same issue with Win10 (server) and Manjaro (client). As described above, the client is not interpreting Capslock as Mod3. The right sided Mod3 works fine however. This doesn't only occur on kbdneo driver, but also on neo-llkh, the low-level keyboard hook driver. Since both drivers result in exactly the same behaviour on the client, I expect the problem rather on Barrier side. Directly plugged keyboards work as intended on either system. On the linux client, `xev -event keyboard` doesn't recognize anything when capslock is pressed. but the capslock LED lights up on the keyboard. As long as I don't press it again, all characters except letters (!) are caps locked: numbers and punctuation characters. I don't fully understand what Mayerch1 means with > Configuration and everything works great after changing the layout of the` Virtual core XTEST keyboard`. Experimenting a bit with that did not make any change to the capslock behaviour.

gitea-mirror commented

2026-05-05 05:24:16 -06:00

Author

Owner

@butonic commented on GitHub (Aug 19, 2020):

I can reproduce this with barrier 2.3.3 on voidlinux as server and win10 as client. any hints on how to debug this would be welcome. Would debug level3 logs help?

@butonic commented on GitHub (Aug 19, 2020): I can reproduce this with barrier 2.3.3 on voidlinux as server and win10 as client. any hints on how to debug this would be welcome. Would debug level3 logs help?

gitea-mirror commented

2026-05-05 05:24:17 -06:00

Author

Owner

@hhelwich commented on GitHub (Aug 25, 2020):

I can also reproduce this with barrier 2.3.3-release-bbd1accb on Ubuntu 18.04 (client and server).

@hhelwich commented on GitHub (Aug 25, 2020): I can also reproduce this with barrier 2.3.3-release-bbd1accb on Ubuntu 18.04 (client and server).

gitea-mirror commented

2026-05-05 05:24:19 -06:00

Author

Owner

@butonic commented on GitHub (Nov 5, 2020):

Corresponding neo issue in https://git.neo-layout.org/neo/neo-layout/issues/517

@butonic commented on GitHub (Nov 5, 2020): Corresponding neo issue in https://git.neo-layout.org/neo/neo-layout/issues/517

gitea-mirror commented

2026-05-05 05:24:20 -06:00

Author

Owner

@Hacki1337 commented on GitHub (Nov 27, 2021):

I can also reproduce this w/ Barrier 2.3.4-release-c43597c2. Windows 11 (server) Arch Linux (client) and neo2 layout. Here all the letters are scrambled completely, special characters inbetween them.

Edit: w/

setxkbmap -device $xinput list --id-only "Virtual cort XTEST keyboard") de neo

in my .xinitrc it kinda works. . is y tho and layer 4 doesnt work properly.

@Hacki1337 commented on GitHub (Nov 27, 2021): I can also reproduce this w/ Barrier 2.3.4-release-c43597c2. Windows 11 (server) Arch Linux (client) and neo2 layout. Here all the letters are scrambled completely, special characters inbetween them. Edit: w/ ```BASH setxkbmap -device $xinput list --id-only "Virtual cort XTEST keyboard") de neo ``` in my `.xinitrc` it kinda works. `.` is `y` tho and layer 4 doesnt work properly.

gitea-mirror commented

2026-05-05 05:24:22 -06:00

Author

Owner

@Marenz commented on GitHub (Aug 30, 2022):

I want to point all participants here to this issue from the mother-project where I did some work on finding the exact commit that broke it, maybe it helps whoever is fixing this:

https://github.com/symless/synergy-core/issues/3259

@Marenz commented on GitHub (Aug 30, 2022): I want to point all participants here to this issue from the mother-project where I did some work on finding the exact commit that broke it, maybe it helps whoever is fixing this: https://github.com/symless/synergy-core/issues/3259

gitea-mirror commented

2026-05-05 05:24:25 -06:00

Author

Owner

@Marenz commented on GitHub (Aug 30, 2022):

Specifically https://github.com/symless/synergy-core/issues/3259#issuecomment-319215668 might be of help?

@Marenz commented on GitHub (Aug 30, 2022): Specifically https://github.com/symless/synergy-core/issues/3259#issuecomment-319215668 might be of help?

No labels

Rows
Columns