I currently have the latest version of EndeavourOS, fresh install yesterday night (18/03/2022). Which means I ran the following to install and install bluetooth: sudo pacman -S --needed bluez bluez-utils
and for my KDE version I’ve installed bluedevil with: sudo pacman -S bluedevil
Startup
To boot bluetooth and activate it, I ran: sudo systemctl enable --now bluetooth
In the attempt of restarting bluetooth with: sudo systemctl restart bluetooth
In both cases I got the following output:
Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xeu bluetooth.service" for details.
By following the prompt I see that I can run systemctl status bluetooth.service
which prints the following
× bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-03-18 12:40:10 CET; 6s ago
Docs: man:bluetoothd(8)
Process: 10929 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE)
Main PID: 10929 (code=exited, status=226/NAMESPACE)
CPU: 7ms
Mar 18 12:40:10 monkey systemd[1]: Starting Bluetooth service...
Mar 18 12:40:10 monkey systemd[10929]: bluetooth.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such file or directory
Mar 18 12:40:10 monkey systemd[10929]: bluetooth.service: Failed at step NAMESPACE spawning /usr/lib/bluetooth/bluetoothd: No such file or directory
Mar 18 12:40:10 monkey systemd[1]: bluetooth.service: Main process exited, code=exited, status=226/NAMESPACE
Mar 18 12:40:10 monkey systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Mar 18 12:40:10 monkey systemd[1]: Failed to start Bluetooth service.
Hopefully this format is good enough and I’d like to thank everyone that can point me in the right direction and help me fix this issue.
this is the output still after reinstalling bluez and trying restart the service.
sudo systemctl enable --now bluetooth
Job for bluetooth.service failed because the control process exited with error code.
See “systemctl status bluetooth.service” and “journalctl -xeu bluetooth.service” for details.
and then systemctl status bluetooth.service gives
systemctl status bluetooth.service
× bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-03-18 20:57:42 IST; 2min 8s ago
Docs: man:bluetoothd(8)
Process: 2788 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE)
Main PID: 2788 (code=exited, status=226/NAMESPACE)
CPU: 3ms
Mar 18 20:57:42 root1234 systemd[1]: Starting Bluetooth service…
Mar 18 20:57:42 root1234 systemd[2788]: bluetooth.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such file or directory
Mar 18 20:57:42 root1234 systemd[2788]: bluetooth.service: Failed at step NAMESPACE spawning /usr/lib/bluetooth/bluetoothd: No such file or directory
Mar 18 20:57:42 root1234 systemd[1]: bluetooth.service: Main process exited, code=exited, status=226/NAMESPACE
Mar 18 20:57:42 root1234 systemd[1]: bluetooth.service: Failed with result ‘exit-code’.
Mar 18 20:57:42 root1234 systemd[1]: Failed to start Bluetooth service.
This was working yesterday. I did a clean install today . . . twice . . . and have the very same issue. When it doesn’t work on a clean install, (and the issue appears to have happened overnight for others as well), I have to believe that it may be a package issue.
$ pacman -Qs bluez
local/bluez 5.64-1
Daemons for the bluetooth protocol stack
local/bluez-libs 5.64-1
Deprecated libraries for the bluetooth protocol stack
local/bluez-tools 0.2.0-5
A set of tools to manage Bluetooth devices for Linux
local/bluez-utils 5.64-1
Development and debugging utilities for the bluetooth protocol stack
My BT still works as desired. Checked my BT Headphones a minute ago.
I’m running XFCE. @Chesonis You also KDE?
Or does it only occur with new installatons?
Hello. I installed EOS about a week ago. I now realized the BT option isn’t showing in my KDE Plasma.
I went about finding out why and I run into all problems mentioned here.
Writing here just to +1 the issue. I hope it will be resolved soon.
I just went through this with someone else on an older install of Antergos that i had converted to Arch. The bluetooth service would fail to start. I found that the generic btusb module was blacklisted in /etc/modprobe.d/xxxxxx .conf file which was similar to what i post here. Can’t remember it’s name but it was for the usb bluetooth adapter. I went through a long process to narrow it down to the module not loading so the service would try to start on boot and fail.
/etc/modprobe.d/rtl87XXusb.conf
I just commented out the blacklist of btusb and it was good to go and now starts every time on boot.