Package: bluez Version: 4.96-2 Severity: important Since upgrading to bluez 4.96-2 today, I now see this message on boot:
Waiting for /dev to be fully populated...udevd[610]: failed to execute '/lib/ude v/bluez-udev' '/lib/udev/bluez-udev --udev': No such file or directory Checking the bluez udev rule, sure enough it references /lib/udev/bluez-udev, which does not exist. Possibly this meant to reference /lib/udev/bluez? - Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.4.16-1 ii libbluetooth3 4.96-2 ii libc6 2.13-21 ii libcap-ng0 0.6.6-1 ii libdbus-1-3 1.4.16-1 ii libglib2.0-0 2.28.6-1 ii libreadline6 6.2-4 ii libudev0 172-1 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 2.28.6-5 ii udev 172-1 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]

