Page MenuHomePureOS Tracker

Pipe key not working (behaves like #~ key) on Librem 13v2 UK device
Closed, DuplicatePublic

Description

I am unable to type bigger-than and less-than with my Librem 13v2 UK laptop configured as a danish keyboard layout - and if reconfiguring to UK english I cannot type pipe or backslash (the characters printed on that key in the lower left corner).

xev reports that the key signals keycode 51 (keysym 0x27, apostrophe) - identical to the signal when pressing the key just right of the return key with characters hash and tilde on it.

NB! Similar to T439 but not indetical: From the description that other issue has two dead keys, this issue is about one key identical to another.

Event Timeline

I use Debian unstable on my laptop.

What version of systemd are you using, if any?

systemd 238-5 (Debian unstable)

mladen added a subscriber: mladen.Sep 11 2018, 13:17

@jonas.smedegaard Can you try with manually removing:

# Purism Librem 13 V2
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v2*:pvr*
 KEYBOARD_KEY_56=backslash

# Purism Librem 13 V3
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v3*:pvr*
 KEYBOARD_KEY_56=backslash

from your /lib/udev/hwdb.d/60-keyboard.hwdb file and see if it will help after a restart? (Or systemd-hwdb update; udevadm trigger)

evtest output of first pressing backslash/pipe key (lower left corner) and then hash/tilde key (just left of return), with pristine udev:

Event: time 1536705976.250768, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536705976.250768, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 1
Event: time 1536705976.250768, -------------- SYN_REPORT ------------
'Event: time 1536705976.367113, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536705976.367113, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 0
Event: time 1536705976.367113, -------------- SYN_REPORT ------------
Event: time 1536705984.751884, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536705984.751884, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 1
Event: time 1536705984.751884, -------------- SYN_REPORT ------------
'Event: time 1536705984.868556, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536705984.868556, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 0
Event: time 1536705984.868556, -------------- SYN_REPORT ------------

evtest output of pressing backslash/pipe key (lower left corner) and hash/tilde key (just left of return), after hacking udev and rebooting:

Event: time 1536709564.528349, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536709564.528349, type 1 (EV_KEY), code 86 (KEY_102ND), value 1
Event: time 1536709564.528349, -------------- SYN_REPORT ------------
<Event: time 1536709564.604897, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536709564.604897, type 1 (EV_KEY), code 86 (KEY_102ND), value 0
Event: time 1536709564.604897, -------------- SYN_REPORT ------------
Event: time 1536709570.295890, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536709570.295890, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 1
Event: time 1536709570.295890, -------------- SYN_REPORT ------------
'Event: time 1536709570.372645, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536709570.372645, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 0
Event: time 1536709570.372645, -------------- SYN_REPORT ------------

After reboot with hacked udev data, my keys behave correctly after udev is loaded, but (still) not in grub.

NB! Some experimentation revealed that the update+refresh trick work only for entries _changed_ - entries _removed_ are still in effect until restart!

stefannagy added a subscriber: stefannagy.EditedOct 30 2018, 13:34

I guess I can confirm this bug.

I'm affected by T486. After removing the lines added by Purism to /lib/udev/hwdb.d/60-keyboard.hwdb I have no problem anymore – when udev is loaded. However, after reading this report here I wanted to see what happens when I hit these keys in GRUB… And this might be some kind of a fun fact, but at least in my case both keys behave like a backslash/pipe key. @jonas.smedegaard If I understand you correctly that's the very opposite of what you experience, right?

(Librem 13 v3, coreboot 4.8.1-Purism-2, German keyboard, Debian testing)