[Pkg-sysvinit-devel] Bug#624125: sysv-rc: CONCURENCY=makefile causes bluetooth rfcomm setup to fail SOMETIMES

[d older]

Package: sysv-rc
Version: 2.88dsf-13.1
Severity: important

Following a clean install ( hence surprised at the debconf data at the end of
this report) on this Eeepc 701 with a valid /etc/bluetooth/rfcomm.conf  about 1
in 4 times the  /dev/rfcomm0 is not created.

'dmesg' simply omits the 'rfcomm initialized' messages, whereas the console
output states "Starting bluetooth: bluetoothd rfcommCan't open RFCOMM control
socket: Address family not supported by protocol " (obtained from cat
/dev/vcs1).

The other 3 times the system starts correctly.

This has also been seen on a clean install of a P4 2.8GHz system ( 1 in around
8 failures) and an updated Lenny to Squeeze P4 3GHz system ( again 1 in 8
failures).

Startup DOES seems to running in the correct order, that is all dependencies
have started prior to bluetooth being started.


In all case re-running /etc/init.d/bluetooth start does create the /dev/rfcomm0
device.



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysv-rc depends on:
ii  debconf [debconf-2.0]       1.5.36.1     Debian configuration management sy
ii  insserv                     1.14.0-2     Tool to organize boot sequence usi
ii  sysvinit-utils              2.88dsf-13.1 System-V-like utilities

Versions of packages sysv-rc recommends:
ii  lsb-base                3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip

Versions of packages sysv-rc suggests:
pn  bum                           <none>     (no description available)
pn  sysv-rc-conf                  <none>     (no description available)

-- debconf information:
  sysv-rc/unable-to-convert:
  sysv-rc/convert-legacy: true


Dave