[Pkg-bluetooth-maintainers] Bug#668192: bluez: 'service bluetooth status' reports 'failed' even when bluetoothd is running

Kai Günther kai.gustav.guenther at googlemail.com
Mon Apr 9 15:29:06 UTC 2012


Package: bluez
Version: 4.99-2
Severity: normal
Tags: upstream

Dear Maintainer,

the command 
  # service bluetooth status
reports:
  bluetooth is not running ... failed!
but
  # ps -C bluetoothd -O ppid
reports
   PID  PPID S TTY          TIME COMMAND
  3657     1 S ?        00:00:00 /usr/sbin/bluetoothd

I was expecting that 'service bluetooth status' will report 'running'.

The commands 'service bluetooth start' and 'service bluetooth stop' work as expected. 'ps' reveals that a bluetoothd process appears and disappears. 

When the daemon is started there is no '/var/run/bluetoothd.pid' file. I had expected to find one, because adding 'set -x' into '/etc/init.d/bluetooth' and re-executing 'service bluetooth status' revealed that there is a test for this file in the script. 
 
Regards,

Kai


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii  dbus          1.5.12-1
ii  kmod          6-2
ii  libc6         2.13-27
ii  libcap-ng0    0.6.6-1
ii  libdbus-1-3   1.5.12-1
ii  libglib2.0-0  2.30.2-6
ii  libreadline6  6.2-8
ii  libudev0      175-3.1
ii  libusb-0.1-4  2:0.1.12-20
ii  lsb-base      4.1+Debian0
ii  python-dbus   0.84.0-3
ii  python-gi     3.1.0-2
ii  udev          175-3.1

bluez recommends no packages.

bluez suggests no packages.

-- no debconf information





More information about the Pkg-bluetooth-maintainers mailing list