Help! PI 3B doesnt see any bluetooth devices and cannot connect at all
-
When using applications menu and Preferences>Bluetooth Manager I get the following error message:
Connection to BlueZ failed
Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.If I try to add a bluetooth device it will load forever and not see any bluetooth devices. It also does not show any paired bluetooth devices. I've tried to play with some files and code but I think I messed some things up and unfortunately, I know nothing about computers and only know how to Google things.
If I run "systemctl status bluetooth" I get the following code:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─override.conf
Active: failed (Result: exit-code) since Mon 2022-05-23 20:52:39 BST; 6min ago
Docs: man:bluetoothd(8)
Process: 3180 ExecStart=/usr/lib/bluetooth/bluetoothd --debug -n (code=exited, status=1/FAILUR
Main PID: 3180 (code=exited, status=1/FAILURE)
Status: "Starting up"May 23 20:52:39 Musaab bluetoothd[3180]: bluetoothd[3180]: src/main.c:parse_config() Key file do
May 23 20:52:39 Musaab bluetoothd[3180]: bluetoothd[3180]: src/main.c:parse_config() Key file do
May 23 20:52:39 Musaab bluetoothd[3180]: bluetoothd[3180]: src/main.c:parse_config() Key file do
May 23 20:52:39 Musaab bluetoothd[3180]: bluetoothd[3180]: src/main.c:parse_config() Key file do
May 23 20:52:39 Musaab bluetoothd[3180]: D-Bus setup failed: Connection ":1.46" is not allowed t
May 23 20:52:39 Musaab bluetoothd[3180]: bluetoothd[3180]: Unable to get on D-Bus
May 23 20:52:39 Musaab systemd[1]: bluetooth.service: Main process exited, code=exited, status=1
May 23 20:52:39 Musaab systemd[1]: Failed to start Bluetooth service.
May 23 20:52:39 Musaab systemd[1]: bluetooth.service: Unit entered failed state.
May 23 20:52:39 Musaab systemd[1]: bluetooth.service: Failed with result 'exit-code'/code]If I do "sudo systemctl restart bluetooth" I get:
Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.If I do "sudo systemctl start bluetooth" I get the same message. This has been very annoying as I mainly use bluetooth speakers, and especially it doesn't work with Retropie which is extremely frustrating. Would appreciate all the help I can get.
Info:
a22082 3B 1.2 BCM2837A0/B0 1GB Embest
Code Model Revision SoC RAM Manufacture (Respectively) -
Seems like you mis-configured your
bluetooth
service and it's not starting anymore. My advice is to remove theoverride.conf
you've added for thesystemd
service and try again to start it. If it doesn't work, maybe start over with a new image ?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.