#579392 bluez: my USB bluetooth dongle gets detected, but I cannot activate it

Package:
gnome-bluetooth
Source:
gnome-bluetooth
Description:
GNOME Bluetooth Send To app
Submitter:
Date:
2025-01-19 01:48:09 UTC
Severity:
important
Tags:
#579392#5
Date:
2010-04-27 14:37:35 UTC
From:
To:
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

#579392#10
Date:
2010-04-28 08:23:18 UTC
From:
To:
reassign 579392 gnome-bluetooth
notfound 579392 4.60-1
found 579392 2.30.0-1
forwarded 579392 https://bugzilla.gnome.org/show_bug.cgi?id=617050
thanks

While the gnome-bluetooth icon still claims my Bluetooth dongle is
disabled, "hcitool scan" reports reasonable results, so it's most
likely a bug in the gnome-bluetooth frontend and not in bluez itself.

  - Fabian

#579392#29
Date:
2014-10-19 18:57:15 UTC
From:
To:
tags 579392 - fixed-upstream
tags 579392 + wontfix
stop

Fabian Greffrath [reporter] 2010-04-30 08:52:10 UTC

Well, either bluetoothd gets improved to also handle non-UTF-8 device names
or bluetoothd does g_utf8_validate as soon as it reads out the device names,
converts faulty strings to UTF-8 and immediately writes them back to the
device. I managed to write a patch that works like this for hciconfig, but not
for the daemon...

#579392#34
Date:
2014-10-20 06:28:36 UTC
From:
To:
Hi Stéphane,
http://marc.info/?l=linux-bluetooth&m=127315737929319&w=2

So, if you confirm that the bug still isn't fixed yet, why do you close
it then?

- Fabian

#579392#39
Date:
2014-10-20 09:04:32 UTC
From:
To:
reopen 579392
tags 579392 - wontfix
stop

Hi Fabian,

Le lundi 20 octobre 2014 à 08:28:36, Fabian Greffrath a écrit :


Apparently this bug does not directly concern gnome-bluetooth and your
patch has not been back since May 2010.

Closed bug was perhaps extreme, sorry, but expect not solve anything
either. Maybe I need to reassign to package bluez and your side revive
discussion list linux-bluetooth.

Regards,

#579392#52
Date:
2025-01-19 01:47:23 UTC
From:
To:
Dear submitter,

as the package gnome-bluetooth has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1093420

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)