Open ianchanning opened 4 months ago
I'm on Ubuntu 22.04.
Running this command (from the Useful commands list)...
rm -r /var/lib/bluetooth/*
... prevents bluetooth from restarting after a reboot. All attempts to get the bluetooth service to start fail.
For example all suggestions in this question fail: https://askubuntu.com/questions/1403817/i-cant-turn-on-bluetooth-in-ubuntu-22-04-lts
The service status has a 226/NAMESPACE error message:
226/NAMESPACE
$ sudo systemctl status bluetooth.service × bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2024-04-21 19:08:23 CEST; 2min 11s ago Docs: man:bluetoothd(8) Main PID: 9746 (code=exited, status=226/NAMESPACE) CPU: 12ms Apr 21 19:08:23 bo-didley systemd[1]: bluetooth.service: Scheduled restart job, restart counter is at 5. Apr 21 19:08:23 bo-didley systemd[1]: Stopped Bluetooth service. Apr 21 19:08:23 bo-didley systemd[1]: bluetooth.service: Start request repeated too quickly. Apr 21 19:08:23 bo-didley systemd[1]: bluetooth.service: Failed with result 'exit-code'. Apr 21 19:08:23 bo-didley systemd[1]: Failed to start Bluetooth service.
Hunting for that error brings up this rather strange answer which suggests running:
sudo install -dm700 /var/lib/bluetooth
This fixes the problem (after a further reboot). If that is the correct command to re-instate the cache, could I suggest adding it to the readme?
I'm on Ubuntu 22.04.
Running this command (from the Useful commands list)...
... prevents bluetooth from restarting after a reboot. All attempts to get the bluetooth service to start fail.
For example all suggestions in this question fail: https://askubuntu.com/questions/1403817/i-cant-turn-on-bluetooth-in-ubuntu-22-04-lts
The service status has a
226/NAMESPACE
error message:Hunting for that error brings up this rather strange answer which suggests running:
This fixes the problem (after a further reboot). If that is the correct command to re-instate the cache, could I suggest adding it to the readme?