I'm not sure we should allow failure to start the daemon to be classified as an install failure...
Okt 23 07:08:46 atom systemd[1]: [0;1;39m[0;1;31m[0;1;39mbluetooth.service: Killing process 636 (bluetoothd) with signal SIGKILL.[0m Okt 23 07:08:46 atom systemd[1]: [0;1;38;5;185m[0;1;39m[0;1;38;5;185mbluetooth.service: Failed with result 'exit-code'.[0m Okt 23 07:08:46 atom systemd[1]: bluetooth.service: Unit process 636 (bluetoothd) remains running after unit stopped. Okt 23 07:08:46 atom systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to start Bluetooth service.[0m dpkg: error processing package bluez (--configure): installed bluez package post-installation script subprocess returned error exit status 1 Setting up libwind0-heimdal:amd64 (7.7.0+dfsg-2) ... ** Summary changed: - package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 + package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901115 Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901115/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
