Package: bluez
Version: 5.50-1
Severity: important
Tags: a11y
Dear Maintainer,
during a usual package update of my debian buster system, dpkg crashed while
upgrading bluez package with following stripped output:
Preparing to unpack .../bluez_5.50-1_amd64.deb ...
Unpacking bluez (5.50-1) over (5.50-1) ...
Processing triggers for systemd (239-7) ...
Processing triggers for man-db (2.8.4-2) ...
Processing triggers for dbus (1.12.10-1) ...
Setting up bluez (5.50-1) ...
Job for bluetooth.service failed because the control process exited with error
code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
invoke-rc.d: initscript bluetooth, action "restart" failed.
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-08-17 00:23:18 CEST; 16ms
ago
Docs: man:bluetoothd(8)
Process: 28974 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited,
status=226/NAMESPACE)
Main PID: 28974 (code=exited, status=226/NAMESPACE)
Aug 17 00:23:18 xxxx systemd[1]: Starting Bluetooth service...
Aug 17 00:23:18 xxxx systemd[28974]: bluetooth.service: Failed to set up mount
namespacing: Bad address
Aug 17 00:23:18 xxxx systemd[28974]: bluetooth.service: Failed at step
NAMESPACE spawning /usr/lib/bluetooth/bluetoothd: Bad address
Aug 17 00:23:18 xxxx systemd[1]: bluetooth.service: Main process exited,
code=exited, status=226/NAMESPACE
Aug 17 00:23:18 xxxx systemd[1]: bluetooth.service: Failed with result 'exit-
code'.
Aug 17 00:23:18 xxxx systemd[1]: Failed to start Bluetooth service.
dpkg: error processing package bluez (--configure):
installed bluez package post-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
bluez
Deactivating Lennart Poetterings directives (ProtectHome= and ProtectSystem=)
for sandbox service inside systemd (see attached patch) seems to cure the
problem temporally. I can continue to use bluetooth normally. However, pulling
down security is generally the wrong direction to go, thus I consider this only
as a first quick fix. I am happy to provide further information upon request
Thanks in advance for assistance and support.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bluez depends on:
ii dbus 1.12.10-1
ii kmod 25-1
ii libasound2 1.1.6-1
ii libc6 2.27-5
ii libdbus-1-3 1.12.10-1
ii libdw1 0.170-0.5
ii libglib2.0-0 2.56.1-2
ii libreadline7 7.0-5
ii libudev1 239-7
ii lsb-base 9.20170808
ii udev 239-7
bluez recommends no packages.
Versions of packages bluez suggests:
ii pulseaudio-module-bluetooth 11.1-5
-- no debconf information
*** /lib/systemd/system/bluetooth.service 2018-08-17 00:27:54.443067522
+0200
--- /etc/systemd/system/bluetooth.target.wants/bluetooth.service.orig
2018-08-16 23:58:13.668972473 +0200
***************
*** 12,19 ****
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
! #ProtectHome=true
! #ProtectSystem=full
[Install]
WantedBy=bluetooth.target
--- 12,19 ----
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
! ProtectHome=true
! ProtectSystem=full
[Install]
WantedBy=bluetooth.target
