Package: bluez Version: 4.63-2 Severity: normal
This bug still exists. Upgrading Testing stopped bluez causing bluetooth keyboard to stop working. No impact for me as upgrade did not require user interaction but this cannot be guaranteed as many other packages are being configured while bluez is disabled. Restarted /etc/init.d/bluetooth using another keyboard while upgrade was continuing to be able to do other things. Bluetooth should be restarted as soon as it is shut down to prevent the system loosing interaction with user. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33.1 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluez depends on: ii dbus 1.2.24-1 simple interprocess messaging syst ii libbluetooth3 4.63-2 Library to use the BlueZ Linux Blu ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst ii libglib2.0-0 2.24.0-1 The GLib library of C routines ii libnl1 1.1-5 library for dealing with netlink s ii libusb-0.1-4 2:0.1.12-14 userspace USB programming library ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-89 creates device files in /dev ii module-init-tools 3.12~pre2-3 tools for managing Linux kernel mo ii udev 153-2 /dev/ and hotplug management daemo bluez recommends no packages. Versions of packages bluez suggests: ii python-dbus 0.83.1-1 simple interprocess messaging syst ii python-gobject 2.21.1-1 Python bindings for the GObject li -- Configuration Files: /etc/bluetooth/audio.conf changed [not included] /etc/bluetooth/rfcomm.conf changed [not included] /etc/default/bluetooth changed [not included] -- 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
