[Pkg-bluetooth-maintainers] Bug#624353: bluez: I can't use bluetooth unless I restart it from /etc/init.d

Ernesto Cuconato e.cuconato at gmail.com
Wed Apr 27 18:55:37 UTC 2011


Subject: bluez: I can't use bluetooth unless I restart it from /etc/init.d
Package: bluez
Version: 4.91-1
Severity: normal

I've used Squeeze and bluetooth has worked well, but, when I upgraded 
to
Wheezy, I get this problem. Bluetooth starts during the boot but I get no
Devices from Bluedevil (and Blueman). If I restart it from /etc/init.d/ I'm
able to use it.
I tried to launch bluez whithout restarting bluetooth and I got this error:

ernesto at Debook:~$ bluez-test-adapter
Traceback (most recent call last):
  File "/usr/bin/bluez-test-adapter", line 10, in <module>
    manager = dbus.Interface(bus.get_object("org.bluez", "/"),
"org.bluez.Manager")
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 244, in 
get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 241, in 
__init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 183, in
activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 281, in
start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 630, in
call_blocking
    message, timeout)
dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.ServiceUnknown: The
name org.bluez was not provided by any .service files

My hardware (from lshw):
configuration: driver=hub slots=2 speed=12Mbit/s
              *-usb
                   description: Bluetooth wireless interface
                   product: Bluetooth HCI
                   vendor: Apple, Inc.
                   physical id: 1
                   bus info: usb at 3:1
                   version: 19.65
                   capabilities: bluetooth usb-2.00
                   configuration: driver=btusb speed=12Mbit/s

Is it a dbus bug?



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable')
Architecture: i386 (i686)

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

Versions of packages bluez depends on:
ii  dbus                         1.4.6-1     simple interprocess messaging 
syst
ii  libbluetooth3                4.91-1      Library to use the BlueZ Linux 
Blu
ii  libc6                        2.11.2-11   Embedded GNU C Library: Shared 
lib
ii  libcap-ng0                   0.6.5-1     An alternate POSIX capabilities 
li
ii  libdbus-1-3                  1.4.6-1     simple interprocess messaging 
syst
ii  libglib2.0-0                 2.28.6-1    The GLib library of C routines
ii  libusb-0.1-4                 2:0.1.12-17 userspace USB programming 
library
ii  lsb-base                     3.2-27      Linux Standard Base 3.2 init 
scrip
ii  module-init-tools            3.12-1      tools for managing Linux kernel 
mo
ii  python-dbus                  0.83.1-1+b1 simple interprocess messaging 
syst
ii  python-gobject               2.28.3-2    Python bindings for the GObject 
li
ii  udev                         167-3       /dev/ and hotplug management 
daemo

bluez recommends no packages.

bluez suggests no packages.

-- no debconf information





More information about the Pkg-bluetooth-maintainers mailing list