[Pkg-bluetooth-maintainers] Bug#555134: bluez: hcid fails because rfkill blocks bt

arne anka debian at ginguppin.de
Sun Nov 8 18:11:52 UTC 2009


Package: bluez
Version: 4.56-2
Severity: normal

i don't really understand, what kernel genius decided to use _one_ rfkill
switch to disable _all_ radios, but anyway, because i use rfkill default
off to disbale wlan, bluetooth is obviously dead, too.

that leads to /etc/init.d/bluetooth somewhat failing when being started:

Nov  8 18:35:59 ginguppin bluetoothd[1245]: Bluetooth daemon 4.56
Nov  8 18:35:59 ginguppin bluetoothd[1245]: Starting SDP server
Nov  8 18:35:59 ginguppin bluetoothd[1245]: Can't load plugin
/usr/lib/bluetooth/plugins/netlink.s
o: /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug
Nov  8 18:35:59 ginguppin bluetoothd[1245]: Can't create GN bridge
Nov  8 18:35:59 ginguppin bluetoothd[1245]: HCI dev 0 registered
Nov  8 18:35:59 ginguppin bluetoothd[1248]: Can't init device hci0:
Unknown error 132 (132)

after some recherche, i had to get sources of that rfkill-tool,
apprently included with most other distributions, at
http://git.sipsolutions.net/?p=rfkill.git;a=snapshot;h=HEAD;sf=tgz
built it and afterwards do

rfkill unblock bluetooth

which made bt magically available again.

so, what i am trying to say, we need in debian either that rfkill tool
(there's some discussion from about july with no apparent result, since
the rfkill tool is still not in debian) or scripts like /etc/init.d/bluetooth
need some help to make sure, bt is enabled when starting (as long
as there is not userland tool available, the init script has to enable
bt, hasn't it? my bt is an usb dongle -- so, there's no switch to make
kernle rfkill aware of bt being en-/disabled).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bluez depends on:
ii  dbus                         1.2.16-2    simple interprocess messaging syst
ii  libbluetooth3                4.56-2      Library to use the BlueZ Linux Blu
ii  libc6                        2.10.1-5    GNU C Library: Shared libraries
ii  libdbus-1-3                  1.2.16-2    simple interprocess messaging syst
ii  libglib2.0-0                 2.22.2-2    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-13 userspace USB programming library
ii  lsb-base                     3.2-23      Linux Standard Base 3.2 init scrip
ii  makedev                      2.3.1-89    creates device files in /dev
ii  module-init-tools            3.11-1      tools for managing Linux kernel mo
ii  udev                         146-6       /dev/ and hotplug management daemo

bluez recommends no packages.

Versions of packages bluez suggests:
ii  python-dbus                   0.83.0-1   simple interprocess messaging syst
ii  python-gobject                2.20.0-1   Python bindings for the GObject li

-- no debconf information





More information about the Pkg-bluetooth-maintainers mailing list