Change Details

Directly related to T431. Librem 13 v2, v3 **US model** devices have a wrong mapping of the pipe key. We introduced a workaround in PureOS and forwarded it upstream. However, the workaround also affects **UK and DE models** which do not have this problem! The result is that the pipe key on these models is now acting like the # key. Removing the lines from `/lib/udev/hwdb.d/60-keyboard.hwdb`: ``` # 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 # Purism Librem 13 V4 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v4*:pvr* KEYBOARD_KEY_56=backslash ``` and running: ``` sudo systemd-hwdb update sudo udevadm trigger ``` __enables correct functioning__ of the pipe key again on **UK** and **DE** models. I suggest the following: 1. Remove the workaround from our systemd as well as removing it from upstream (hardware manufacturer should deal with the bug at the //keyboard EC firmware// level themselves); 2. For affected hardware create a separate package with the workaround,and instruct users with the hardware to install the package. Another solution: Create a package with hwdb files that will revert this workaround from systemd and instruct users with Librem 13 UK/DE devices to install it.

Directly related to T431. Librem 13 v2, v3 **US model** devices have a wrong mapping of the pipe key. We introduced a workaround in PureOS and forwarded it upstream. However, the workaround also affects **UK and DE models** which do not have this problem! The result is that the pipe key on these models is now acting like the # key. A stable workaround is to add file `/etc/udev/hwdb.d/70-keyboard.hwdb`: ``` # Purism Librem 13 V2/V3/V4 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v[2-4]*:pvr* KEYBOARD_KEY_56=102nd ``` and running: ``` sudo systemd-hwdb update sudo udevadm trigger ``` which __enables correct functioning__ of the pipe key again on **UK** and **DE** models. I suggest the following: 1. Remove the workaround from our systemd as well as removing it from upstream (hardware manufacturer should deal with the bug at the //keyboard EC firmware// level themselves); 2. For affected hardware create a separate package with the workaround,and instruct users with the hardware to install the package. Another solution: Create a package with hwdb files that will revert this workaround from systemd and instruct users with Librem 13 UK/DE devices to install it.

Directly related to T431. Librem 13 v2, v3 **US model** devices have a wrong mapping of the pipe key. We introduced a workaround in PureOS and forwarded it upstream. However, the workaround also affects **UK and DE models** which do not have this problem! The result is that the pipe key on these models is now acting like the # key. Removing the lines from `/libA stable workaround is to add file `/etc/udev/hwdb.d/670-keyboard.hwdb`: ``` # 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 # Purism Librem 13 V2/V3/V4 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v4[2-4]*:pvr* KEYBOARD_KEY_56=backslash102nd ``` and running: ``` sudo systemd-hwdb update sudo udevadm trigger ``` which __enables correct functioning__ of the pipe key again on **UK** and **DE** models. I suggest the following: 1. Remove the workaround from our systemd as well as removing it from upstream (hardware manufacturer should deal with the bug at the //keyboard EC firmware// level themselves); 2. For affected hardware create a separate package with the workaround,and instruct users with the hardware to install the package. Another solution: Create a package with hwdb files that will revert this workaround from systemd and instruct users with Librem 13 UK/DE devices to install it.