Your message dated Sat, 17 Aug 2024 17:04:33 +0900
with message-id
<mcfmxvmirb3behsyxkfha65xiwp25kc25gpa4vw75oaoaauxuk@eb6kbizmlcvt>
and subject line Close bug
has caused the Debian Bug report #997853,
regarding bluetooth.service: Failed to locate executable
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 [email protected]
immediately.)
--
997853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997853
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bluetooth
Version: 5.55-3.1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
After a recent full-upgrade from buster to bullseye, bluetooth is not working.
It appears the system is looking for the bluetooth daemon executable in the
/usr/lib/bluetooth/ directory
but no such directory exists. There is a directory called
/usr/libexec/bluetooth/
that has a bluetoothd executable. I have tried reinstalling almost all the
bluetooth-related packages
hoping it might solve the issue by creating missing symlinks or whatever but it
did not.
I also have the bluez package installed and I wasn't certain which package to
file this bug against.
The output of "systemctl status bluetooth" gives:
bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─01-disable-sap-plugin.conf
Active: failed (Result: exit-code) since Tue 2021-10-26 12:25:19 +08; 8min
ago
Docs: man:bluetoothd(8)
Process: 4917 ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap
(code=exited, status=203/EXEC)
Main PID: 4917 (code=exited, status=203/EXEC)
CPU: 4ms
Oct 26 12:25:19 mycomputername systemd[1]: Starting Bluetooth service...
Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed to
locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory
Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed at step
EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory
Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Main process
exited, code=exited, status=203/EXEC
Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Failed with
result 'exit-code'.
Oct 26 12:25:19 mycomputername systemd[1]: Failed to start Bluetooth service.
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bluetooth depends on:
ii bluez 5.55-3.1
bluetooth recommends no packages.
Versions of packages bluetooth suggests:
ii bluez-cups 5.55-3.1
pn bluez-meshd <none>
ii bluez-obexd 5.55-3.1
--- End Message ---
--- Begin Message ---
Hi,
This was a problem caused by overriding configuration files.
So close this bug.
Thanks,
Nobuhiro
--- End Message ---
