[Pkg-bluetooth-maintainers] Bug#754830: bluez: rfcomm and bluetoothd fail to start

[Cristian Ionescu-Idbohrn]

Package: bluez
Version: 5.21-1
Severity: grave

/etc/init.d/bluetooth fails to start.
First:

	Starting bluetooth: bluetoothd rfcomm/usr/bin/rfcomm: invalid option -- 'f'

After editing the file and removing that option, next thing coms up:

	Starting bluetooth: bluetoothd rfcommMissing dev parameter

Still, everything is reported with an [ ok ] message, which is confusing
at best.

I identified two other bug reports pointing in the same direction:

	712386  [bluez] invalid option passed to rfcomm tool
	737502  bluez: conffiles not removed

reported already on some experimental version.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii  dbus                 1.8.6-1
ii  init-system-helpers  1.19
ii  kmod                 18-1
ii  libc6                2.19-7
ii  libdbus-1-3          1.8.6-1
ii  libglib2.0-0         2.40.0-3
ii  libreadline6         6.3-6
ii  libudev1             204-14
ii  lsb-base             4.1+Debian13
ii  udev                 204-14

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory: '/etc/init.d/bluetooth'

Yes.  The attempt to make it work:

--- /etc/init.d/bluetooth.orig	2014-06-27 21:50:43.000000000 +0200
+++ /etc/init.d/bluetooth.mine	2014-07-14 18:39:02.721719759 +0200
@@ -103,14 +103,17 @@

 start_rfcomm()
 {
-	if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+#	if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+	if [ -x $RFCOMM ] ; then
 		# rfcomm must always succeed for now: users
 		# may not yet have an rfcomm-enabled kernel
                 if [ "$VERBOSE" != no ]; then
 		       log_progress_msg "${RFCOMM##*/}"
-		       $RFCOMM -f $RFCOMM_CONF bind all || :
+#		       $RFCOMM -f $RFCOMM_CONF bind all || :
+		       $RFCOMM bind all || :
                 else
-		       $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+#		       $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+		       $RFCOMM bind all >/dev/null 2>&1 || :
                 fi
 	fi
 }
@@ -129,14 +132,17 @@

 restart_rfcomm()
 {
-	if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+#	if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+	if [ -x $RFCOMM ] ; then
                if [ "$VERBOSE" != no ]; then
 		       log_progress_msg  "${RFCOMM##*/}"
 		       $RFCOMM unbind all || :
-		       $RFCOMM -f $RFCOMM_CONF bind all || :
+#		       $RFCOMM -f $RFCOMM_CONF bind all || :
+		       $RFCOMM bind all || :
                else
 		       $RFCOMM unbind all >/dev/null 2>&1|| :
-		       $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+#		       $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+		       $RFCOMM bind all >/dev/null 2>&1 || :
                fi
 	fi
 }

-- no debconf information