[Pkg-bluetooth-maintainers] Bug#579392: bluez: my USB bluetooth dongle gets detected, but I cannot activate it

[Fabian Greffrath]

Package: bluez
Version: 4.60-1
Severity: important

Hi,

I have an USB bluetooth dongle that gets detected as the following device by
lsusb:

        Bus 006 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

As soon as I plug it into my computer, the gnome-bluetooth icon appears in the
notification area (with a red [x] though) and dmesg reports the following:

        [   52.744010] usb 6-2: new full speed USB device using uhci_hcd and
address 2
        [   52.912055] usb 6-2: New USB device found, idVendor=0a12,
idProduct=0001
        [   52.912058] usb 6-2: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
        [   52.912140] usb 6-2: configuration #1 chosen from 1 choice
        [   52.962674] Bluetooth: Generic Bluetooth USB driver ver 0.6
        [   52.964730] usbcore: registered new interface driver btusb

Now when I open bluetooth-properties to actually activate the dongle the
following messages are reported on my terminal:

        ** Message: adding killswitch idx 1 state 1
        ** Message: killswitch 1 is 1
        ** Message: killswitches state 1

[Now I click on the "Activate bluetooth" button.]

        ** Message: RFKILL event: idx 1 type 2 op 2 soft 0 hard 0

        ** Message: killswitch 1 is 1
        ** Message: killswitches state 1

However, nothing really happens, i.e. the "Activate bluetooth" button is greyed
out, the Bluetooth icon in the notification area still shows the red cross and
the computer can neither be found by other bluetooth devices nor find some
itself (e.g. via nautilus-sendto).

It may be worth noting that I experienced this bug for a while already but was
never able to reproduce which package actually broke it, as I only realized it
after a series of huge dist-upgrades. I tried several combinations of
linux-2.6, bluez and gnome-bluetooth packages, but never found a working
solution again. I also already tried 4.63-1 which is currently in Debian
incoming, but without success. If there is any more information I can provide
to help getting this fixed, please let me now!

Cheers,
Fabian



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (550, 'unstable'), (400, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-4-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii  dbus                         1.2.24-1    simple interprocess messaging syst
ii  libbluetooth3                4.60-1      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-1       /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

-- no debconf information