Bluetooth keyboard unavailable during LUKS disk unlocking

[Robert Hensing]

I need to keep a spare USB keyboard around to be able to boot my system. Having bluetooth keyboard support in initramfs would make that unnecessary.

A trimmed down bluez in the initramfs will solve the problem. It would also need access to a copy of /var/lib/bluetooth in, say, /boot/bluetooth.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[robau (rob-audenaerde-org)]

I also suffer from this 'missing functionality'. Please add this option!

[Markus Spring (m-spring)]

Same problem here - no encryption is not an option, but my bluetooth keyboard is more than just "nice to have".

[zwigno (zwigno)]

FYI it looks like Fedora has implemented this - https://github.com/dracutdevs/dracut/pull/1139 but it may not pick up all bluetooth keyboards yet (grep -qiE 'Class=0x[0-9a-f]{3}5[4c]0' /var/lib/bluetooth/*/*/info) failed to find my Logi ERGO K860.)

[Thorsten Merten (thorsten-merten)]

@zwingo (and for reference if somebody wants to tackle this):

Same keyboard here with an MX Master mouse. Both devices (and some other bluetooth devices iiuc) do not indicate a class in `/var/lib/bluetooth/*/*/info`.

However, I think one could grep for Bluetooth Appearance values in addition:

```
APPEARANCE_HID_KEYBOARD 961 --> works for K860 keyboard (Appearance=0x03c1)
APPEARANCE_HID_MOUSE 962 --> works for MX Master (Appearance=0x03c2)
```