Package: bluez-utils Version: 3.13-1 Severity: important Tags: patch
if you enable dund (DUND_ENABLED=1) in /etc/default/bluetooth it will not be able to connect to the internal SDP in hcid, This should probably be fixed by having the init.d script check wheter SDP is ready or not, but a quick workaround was tweaking the /etc/init.d/bluetooth adding a delay in the start-case, reodering + adding delay in restart-case. Patch (diff -u) for workaround is attached. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23.9 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages bluez-utils depends on: ii dbus 1.1.2-1 simple interprocess messaging syst ii libbluetooth2 3.20-1 Library to use the BlueZ Linux Blu ii libc6 2.7-3 GNU C Library: Shared libraries ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst ii libglib2.0-0 2.14.4-2 The GLib library of C routines ii libusb-0.1-4 2:0.1.12-8 userspace USB programming library ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii makedev 2.3.1-84 creates device files in /dev ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo ii udev 0.114-2 /dev/ and hotplug management daemo Versions of packages bluez-utils recommends: ii bluez-gnome 0.13-1 Bluetooth utilities for GNOME -- no debconf information
--- /etc/init.d/bluetooth.ORIG 2007-08-02 18:06:40.000000000 +0200 +++ /etc/init.d/bluetooth 2007-12-07 11:40:03.047739282 +0100 @@ -245,6 +245,7 @@ enable_hci_input || true fi start_rfcomm || true + sleep 3 start_pan || true log_end_msg 0 ;; @@ -279,8 +280,9 @@ fi start-stop-daemon --start --quiet --exec $HCID -- $HCID_OPTIONS || true log_progress_msg "hcid" - start_pan || true start_hid || true + sleep 3 + start_pan || true restart_rfcomm log_end_msg 0 ;;