Client keyboard layout is used instead of host one

[mirh]

Operating Systems

Server: Windows 7

Client: Manjaro Linux

Barrier Version

2.31 git/snapshot

Steps to reproduce bug

1. Have some random keyboard layout (italian in my case)
2. Write from the keyboard on the host to the client

Other info

Not sure if this couldn't have something to do with #45

[mirh]

I found out
setxkbmap $(setxkbmap -query | grep "^layout:" | awk -F ": *" '{print $2}')
fixed it.
It'd be nice if this wasn't needed on every reboot though, I guess?

[mirh]

Ok I understood more the culprit.
On linux (that is, my client) I had set my keyboard layout to it, us (that is: two in order of preference).
Somehow barrier is always using the last one.

Which seems actually wrong on two levels
a) the preference is obviously from the one with more priority to the lower
b) shouldn't the thing be using my host settings to begin with?

[AdrianKoshka]

shouldn't the thing be using my host settings to begin with?

One would assume so.

[eNTi]

Hi. Having the exact same issue. Server: Windows 10, Client: Artix Linux.

It's always using the default us layout instad of my preferred one. It's also ignoring any settings I've put into my Xorg config, so my CAPSLOCK key doesn't work as Meta4 which makes things a lot more complicated for me.

[mirh]

Ok, I'm pretty dumb.
I also experienced similar breakages after just having added a third layout (no barrier involved at all!)
And it just turns out that if you don't have the keyboard widget "making sure you are actually using the right one" in the windows, the autoselection shenanigans in the DE might go nuts.

Because the xkbmap list isn't possibly even about preferences.. It's most essentially an unordered set of available choices.

I guess like the transition/hook/switch barrier does, somehow, someway, whatevs, triggered the same "innocent" behaviors.
So at the end of the day, it's quite a simpler problem to fix.

Even though, now I'm wondering a) if you should take into account that host and clients could have different layout "lists" b) how you could even override one with the other
EDIT: turns out en-us really get the preferential treatment #1298