Package: bluez Version: 4.97-1 Severity: normal Because hci2hid is called when udev starts, any affected HID devices become unusable until bluetooth is started. In particular this affects cryptdisks (and cryptdisks-early) which rely on the keyboard for entering the passphrase.
It would be helpful if the udev rule in /lib/udev/rules.d/97-bluetooth-hid2hci.rules were to check whether the bluetooth daemon had started, and if not, delay calling hid2hci, say by writing the command into a file that /etc/init.d/bluetooth will run when starting bluetooth. For completeness sake, it could also set up a command to return the device to HID mode when stopping the bluetooth daemon. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluez depends on: ii dbus 1.4.16-1 ii libc6 2.13-23 ii libcap-ng0 0.6.6-1 ii libdbus-1-3 1.4.16-1 ii libglib2.0-0 2.30.2-4 ii libreadline6 6.2-8 ii libudev0 175-3 ii libusb-0.1-4 2:0.1.12-19 ii lsb-base 3.2-28 ii module-init-tools 3.16-1 ii python-dbus 0.84.0-2 ii python-gobject 3.0.3-1 ii udev 175-3 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
