Bluetooth adapter disables automatically

[Vishesh Handa]

Hi, I recently bought a Bluetooth dongle, and it worked perfectly initially until I decided to switch it off using the popup menu of blueman, and since then it just refuses to work no matter what I do.

On typing
vishesh@vishesh-desktop:~$ lsusb | grep Blue
Bus 003 Device 003: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Here is /var/log/syslog (Appropriate section )
Today 00:01:23 vishesh-desktop kernel [19715.408021] usb 3-1: new full speed USB device using uhci_hcd and address 3
Today 00:01:23 vishesh-desktop kernel [19715.563701] usb 3-1: configuration #1 chosen from 1 choice
Today 00:01:23 vishesh-desktop bluetoothd[12820] Bluetooth daemon 4.57
Today 00:01:23 vishesh-desktop bluetoothd[12821] Starting SDP server
Today 00:01:23 vishesh-desktop bluetoothd[12821] Can't load plugin /usr/lib/bluetooth/plugins/netlink.so: /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug
Today 00:01:23 vishesh-desktop bluetoothd[12821] bridge pan0 created
Today 00:01:23 vishesh-desktop bluetoothd[12821] HCI dev 0 registered
Today 00:01:23 vishesh-desktop NetworkManager SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan0, iface: pan0)
Today 00:01:23 vishesh-desktop NetworkManager SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found.
Today 00:01:23 vishesh-desktop NetworkManager <WARN> device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Today 00:01:23 vishesh-desktop bluetoothd[12821] HCI dev 0 up
Today 00:01:23 vishesh-desktop bluetoothd[12821] Starting security manager 0
Today 00:01:23 vishesh-desktop bluetoothd[12821] Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Today 00:01:23 vishesh-desktop bluetoothd[12821] probe failed with driver input-headset for device /org/bluez/12820/hci0/dev_00_21_08_61_7F_6F
Today 00:01:23 vishesh-desktop bluetoothd[12821] Adapter /org/bluez/12820/hci0 has been enabled
Today 00:01:23 vishesh-desktop bluetoothd[12821] Stopping security manager 0
Today 00:01:23 vishesh-desktop bluetoothd[12821] HCI dev 0 down
Today 00:01:23 vishesh-desktop bluetoothd[12821] Adapter /org/bluez/12820/hci0 has been disabled
Today 00:05:01 vishesh-desktop CRON[25393] (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Today 00:10:50 vishesh-desktop kernel [20282.440025] usb 1-2: new high speed USB device using ehci_hcd and address 9

As you can clearly see it starts and shuts down immediately. An rfkill shows it to be NOT blocked. Here is a somewhat more detailed report http://ubuntuforums.org/archive/index.php/t-1327299.html
It's the thread where I was asking for help. Never eventually got any. Now one month later. I'm filling a bug report :-\

I think Ubuntu generated most of the info you need (or I hope so), but if you need anything else please let me know.

EDIT : I forgot to add that I booted in from a live cd and the bluetooth dongle worked perfectly. So there isn't any hardware problem - I think.

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vishesh 2052 F.... pulseaudio
                      vishesh 2156 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x90320000 irq 22'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,8086d701,00100101'
   Controls : 28
   Simple ctrls : 17
Date: Mon Dec 7 00:16:14 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=50c0a9b0-15d3-48cb-926c-c75ad0c8f34c
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 pan0 no wireless extensions.
Package: linux-image-2.6.31-16-generic 2.6.31-16.52
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=49baf3f9-e920-459d-9566-2901b286f045 ro splash
ProcEnviron:
 LANGUAGE=
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-16-generic N/A
 linux-firmware 1.25
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-16-generic i686
WpaSupplicantLog:

XsessionErrors:
 (nautilus:2182): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2805): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 07/30/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: ECG3510M.86A.0106.2008.0730.1746
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG35EC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29266-207
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrECG3510M.86A.0106.2008.0730.1746:bd07/30/2008:svn:pn:pvr:rvnIntelCorporation:rnDG35EC:rvrAAE29266-207:cvn:ct3:cvr:

[Boris (boris-guskee)]

Try "sudo rm -rf /var/lib/bluetooth/*" and restart the bluetooth demon. Worked with me.

[Martin von Wittich (martin.von.wittich)]

Yes, this is really annoying. /etc/init.d/bluetooth restart kills bluetooth for sure and usually the only way to revive it is to reboot.

[papukaija (papukaija)]

This bug is affecting 2 people.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.