A parallel native Manjaro Linux installation produces the same issue.
But: when live-booting into Arch Linux 3.17.4-1-ARCH, both of the above keys work as they should, before and after doing
root@archiso ~ # loadkeys de-latin1
(which I used to do on a Lenovo T440 with German keyboard layout.)
Can anybody recommend a workaround for this (PureOS?!) issue? Any suggestions welcome. I am stuck and out of ideas, the new machine is sitting lonely in a corner catching the dust. Poor thing.
Since you asked for it, buy El-Cheapo™ €5 USB keyboard and use that until proper fix is available from Purism. Not that great suggestion, but I am under impression that this issue is not fixable in software…
Edit: Also, contact technical support via mail (https://puri.sm/contact/), so they can support you better.
AFAIK the special key code mapping was contributed to debian upstream so that up-to-date distros like Arch Linux (which compiles from up-to-date sources) may already have incorporated this patch.
@max4: Do you use the latest recent version of Qubes 4.0 or you did an upgrade?
German keyboard with german layout and en_UK.utf8 locale is working fine for me.
I didn’t have to set any key codes.
@max4: Yes true, that’s the more interesting part, cause of the embedded controller firmware.
Just was wondering. So, no problem. It’s looks like the same issue, but it’s slightly different.
The patches don’t work for the german keyboard and the issue occurs mostly only in PureOS.
EDIT: I removed the quote of @elsurion’s post, as it was not displayed properly here (missing space before “KEYBOARD_KEY_56…”). Thanks for pointing it out, @Caliga.
Sure. Put a space in front of the second line, just as @elsurion has. You’re welcome
Hm… @antimon maybe you can fix or remove the quote in your message to avoid confusion?
Tried your suggestion step by step which worked out fine, but still having the same wrong mapping on the german keyboard # ’ ’ instead angle brackets & pipe.
Had to create the folder hwdb.d myself. Didn’t exist. Might that have to do with that nothing changed?
I had this issue when upgrading a Librem 13 v3 from Debian 9 stable to unstable. With stable, the <, > and | key worked, after upgrading to unstable and rebooting it did not anymore. @elsurion’s solution had to be adjusted a bit, replacing the “v2” with a “v3” - also see https://tracker.pureos.net/T486