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
