I tried something as suggested in the Matrix group. On boot I did
`rcctl stop xenodm` (as I have been already), then it was suggested that
I run
`apm -z`. I let my computer suspend, started it, then ran
`/usr/local/bin/startsway.sh`
and my keyboard layout was correct. Tab and delete weren't working, but it
at least put everything in the right order.
Thank you for your work and time,
Courtney
On 1/17/24 13:26, Courtney wrote:
Strange. I do only have one physical keyboard attached. I'm assuming
there
is something to do with the wskbd stuff though and however that works. I
assume I can find that info in a man page somewhere?
Courtney
On 1/17/24 12:33, Matthieu Herrb wrote:
On Wed, Jan 17, 2024 at 11:12:53AM -0800, Courtney wrote:
I'm not sure how exactly to report on this one. I installed sway and
other
related wayland and sway packages. I stopped xenodm, used the default
configuration file and started sway with /usr/local/bin/startsway.sh
and
found my keyboard layout was shifted up 2 rows, and jumbled up a huge
amount. For example, 1,2,3,4 became a,s,d,f and y became enter and
k became backspace. It is incredibly awkward to type to find out any
info
on why this is happening since no key is as it would seem. I have to
hard
reset my desktop to get out of sway, but I am baffled by this behavior.
Any advice on how to dig deeper?
Hi,
this is a known issue with the current version of
libinput-openbsd. When you have multiple keyboards of different types
(pckbd aka PS/2 and USB for instance) attached.
Each type has its own keycodes set, translated to evdev-like events in
libinput. The current code can only handle one keyboard at a time and
thus it's the last one attaching to the wskbd mux which "wins". Other
keyboards are translated incorrectly.
This is going to be fixed at some point. In the mean time, try to make
sure you have only one keyboard attached to the mux.
