Your message dated Sun, 9 Apr 2017 06:02:50 +0900
with message-id
<cabmqnvjvvkqw1vvdvt5o3mn5jjmbthzgzt0kytujwpjw1wg...@mail.gmail.com>
and subject line Re: bluez: bluetooth.service doesn't start with systemd
has caused the Debian Bug report #853207,
regarding bluez: bluetooth.service doesn't start with systemd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
853207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bluez
Version: 5.43-1
Severity: grave
Justification: renders package unusable
# systemctl restart bluetooth.service
# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
Active: inactive (dead)
Docs: man:bluetoothd(8)
When running systemd on Unstable the bluetooth daemon doesn't start and NOTHING
is logged about it.
It is possible that my laptop (the only PC I own with bluetooth hardware) is
somehow unsuitable for running bluetooth. It could be that bluetooth is
exiting for a correct reason but the total lack of any logs (either in stdout/
stderr or in syslog) means that I can't determine if this is the case.
If I run /usr/lib/bluetooth/bluetoothd from the command-line as root it appears
to basically work (bluetoothctl will talk to it) so it seems to be something
related to the service file.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages bluez depends on:
ii dbus 1.10.14-1
ii init-system-helpers 1.47
ii kmod 23-2
ii libc6 2.24-9
ii libdbus-1-3 1.10.14-1
ii libglib2.0-0 2.50.2-2
ii libreadline7 7.0-2
ii libudev1 232-14
ii lsb-base 9.20161125
ii udev 232-14
bluez recommends no packages.
Versions of packages bluez suggests:
pn pulseaudio-module-bluetooth <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: severity -1 normal
Control: tags -1 unreproducible
>> Control: tags 853207 + moreinfo
>>
>> Hi,
>>
>> > Most likely the bluetooth support for your laptop is broken under linux.
>> >
>> > The bluetooth.service file contains
>> >
>> > ConditionPathIsDirectory=/sys/class/bluetooth
>> >
>> > which means that systemd only tries to start the bluetooth daemon when
>> > the bluetooth module from the kernel is loaded which creates the above
>> > directory in sysfs. The bluetooth module is in turn only loaded by the
>> > kernel/udev when bluetooth hardware is detected. So the .service file
>> > behaves correctly as to only start the daemon when there is actual
>> > bluetooth hardware available.
>> >
>> > Could you check if the above reasoning is correct by first directly
>> > loading the bluetooth kernel module (modprobe bluetooth), which should
>> > create /sys/class/bluetooth and then trying to start the bluetooth
>> > daemon (systemctl restart bluetooth.service)?
>> >
>> > If that is the case the bug should be reassigned as a wishlist bug to
>> > systemd. If a condition for starting a service is not satisfied when a
>> > user explicitly tries to explicitly start it on the command line, it
>> > would be useful to report the reason for the startup failure to the
>> > user. This would significantly help a user to debug such an issue.
>> >
>>
>> Matthias, thanks for your support.
>> I confirmed this bug with stretch, but the same problem did not happen.
>>
>> Russell, could you confirm again with Matthias's comment?
>
>Cc'ing Russel, as apparently you didn't Cc him.
Emilio, thanks.
I did not receive reply from Russell, but I confirmed that this problem will not
occur in multiple environments.
I changed severity to normal, and I set unreproducible tag to this bug.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--- End Message ---
