@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) ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/993843 Title: Bluetooth keyboard unavailable during LUKS disk unlocking Status in initramfs-tools package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/993843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
