Unable to make bluetooth enabled on boot

Zirum · 20 January 2025 09:31

Hello,

I have a small issue that has been annoying me for a while now.

No matter what I do, I am not able to make bluetooth enable after boot. It's always disabled, but works just fine to enable it manually.

I have tried:

AutoEnable=true in /etc/bluetooth/main.conf
sudo systemctl enable bluetooth
rfkill unblock bluetooth
Reboot after above

Any tips to help a lost lad?

Running Zorin Pro 17 on Lenovo Yoga 920.

zenzen · 20 January 2025 10:42

After rebooting the computer, before you manually start the bluetooth service, can you run sudo systemctl status bluetooth? That might show an error message or point to the cause of the issue.

Zirum · 20 January 2025 11:18

Appreciate your willingness to help debug a bit further, zenzen!

Here's the output I get:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2025-01-20 12:10:06 CET; 40s ago
       Docs: man:bluetoothd(8)
   Main PID: 1067 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18690)
     Memory: 2.5M
        CPU: 71ms
     CGroup: /system.slice/bluetooth.service
             └─1067 /usr/lib/bluetooth/bluetoothd

jan. 20 12:10:06 Zirum-Yoga-920-13IKB bluetoothd[1067]: Too small Add Device complete event
jan. 20 12:10:06 Zirum-Yoga-920-13IKB bluetoothd[1067]: Too small Add Device complete event
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc_xq_453
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc_xq_453
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc_xq_512
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc_xq_512
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc_xq_552
jan. 20 12:10:14 Zirum-Yoga-920-13IKB bluetoothd[1067]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc_xq_552

It reports "Active" from console, but are disabled in systray and under Settings. Maybe not the same "thing"?

Will try to google a bit more on "Too small Add Device complete event" as I did not find any immediate suggestions to test from here.

Edit (if its relevant): Enabling and disabling from systray does not change anything reported in terminal.

Ponce-De-Leon · 20 January 2025 11:42

You only wrote bluetooth. You should try it with bluetooth.service instead:

sudo systemctl enable bluetooth.service

sudo systemctl start bluetooth.service

zenzen · 20 January 2025 11:51

The file extension can be omitted; systemd will assume you mean to use .service.

I seem to remember this was a problem because something interfered with it, but I couldn't quite get what that was...

For reference:

Zirum · 20 January 2025 11:54

As zenzen indicated, did not fix the problem.

But noticed some odd behaviour.
After boot, running sudo systemctl start|stop bluetooth does not change systray indicator.

After I have manually clicked systray icon, same command toggle systray icon as expected.

Zirum · 20 January 2025 11:59

Just for fun, I tested to comment out the AutoEnable, followed by enabling the service. But no progress with that attempt

zenzen · 20 January 2025 12:47

Try to run journalctl -f in the terminal, and then switch bluetooth on. That might show some messages in real time. Maybe that shows something else more useful...

Ponce-De-Leon · 20 January 2025 14:00

Did You checked if in Your BIOS Your Bluetooth is on by default?

Zirum · 20 January 2025 14:28

Did a reboot and tested misc. scenarios with two terminals, though not able to deduct much of it on my end...

Zirum@Zirum-Yoga-920-13IKB:~$ journalctl -f
jan. 20 15:14:08 Zirum-Yoga-920-13IKB gnome-shell[4132]: [ERROR glean_core::metrics::ping] Invalid reason code active for ping usage-reporting
jan. 20 15:14:08 Zirum-Yoga-920-13IKB systemd[1]: systemd-fsckd.service: Deactivated successfully.
jan. 20 15:14:09 Zirum-Yoga-920-13IKB systemd-timesyncd[576]: Initial synchronization to time server 185.125.190.56:123 (ntp.ubuntu.com).
jan. 20 15:14:11 Zirum-Yoga-920-13IKB systemd[1]: systemd-timedated.service: Deactivated successfully.
jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: pcieport 0000:00:1c.4: AER: Multiple Correctable error message received from 0000:6b:00.0
jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: ath10k_pci 0000:6b:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: ath10k_pci 0000:6b:00.0:   device [168c:003e] error status/mask=00000081/00006000
jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: ath10k_pci 0000:6b:00.0:    [ 0] RxErr                  (First)
jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: ath10k_pci 0000:6b:00.0:    [ 7] BadDLLP               
jan. 20 15:14:21 Zirum-Yoga-920-13IKB systemd[1]: systemd-hostnamed.service: Deactivated successfully.
jan. 20 15:14:32 Zirum-Yoga-920-13IKB systemd[1]: systemd-localed.service: Deactivated successfully.
jan. 20 15:14:51 Zirum-Yoga-920-13IKB systemd[1804]: Started Application launched by gnome-session-binary.
jan. 20 15:14:51 Zirum-Yoga-920-13IKB systemd[1804]: Started Application launched by gnome-session-binary.
jan. 20 15:15:51 Zirum-Yoga-920-13IKB systemd[1804]: Started Application launched by gnome-session-binary.

# Execute "sudo systemctl start bluetooth" in parallel terminal
jan. 20 15:15:57 Zirum-Yoga-920-13IKB sudo[4598]:   Zirum : TTY=pts/1 ; PWD=/home/Zirum ; USER=root ; COMMAND=/usr/bin/systemctl start bluetooth
jan. 20 15:15:57 Zirum-Yoga-920-13IKB sudo[4598]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
jan. 20 15:15:57 Zirum-Yoga-920-13IKB sudo[4598]: pam_unix(sudo:session): session closed for user root
# Result: Bluetooth inactive in systray

# Execute "sudo systemctl stop bluetooth" in parallel terminal
jan. 20 15:16:30 Zirum-Yoga-920-13IKB sudo[4622]:   Zirum : TTY=pts/1 ; PWD=/home/Zirum ; USER=root ; COMMAND=/usr/bin/systemctl stop bluetooth
jan. 20 15:16:30 Zirum-Yoga-920-13IKB sudo[4622]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Terminating
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc
jan. 20 15:16:30 Zirum-Yoga-920-13IKB systemd[1]: Stopping Bluetooth service...
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552
jan. 20 15:16:30 Zirum-Yoga-920-13IKB dbus-daemon[756]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.84" (uid=1000 pid=1814 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.25" (uid=0 pid=1064 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
jan. 20 15:16:30 Zirum-Yoga-920-13IKB dbus-daemon[756]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.84" (uid=1000 pid=1814 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.25" (uid=0 pid=1064 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Stopping SDP server
jan. 20 15:16:30 Zirum-Yoga-920-13IKB bluetoothd[1064]: Exit
jan. 20 15:16:30 Zirum-Yoga-920-13IKB systemd[1]: bluetooth.service: Deactivated successfully.
jan. 20 15:16:30 Zirum-Yoga-920-13IKB systemd[1]: Stopped Bluetooth service.
jan. 20 15:16:30 Zirum-Yoga-920-13IKB sudo[4622]: pam_unix(sudo:session): session closed for user root
# Result: Bluetooth inactive in systray. Activate bluetooth button in systray is unresponsive.

# Execute "sudo systemctl start bluetooth" in parallel terminal
jan. 20 15:16:56 Zirum-Yoga-920-13IKB sudo[4630]:   Zirum : TTY=pts/1 ; PWD=/home/Zirum ; USER=root ; COMMAND=/usr/bin/systemctl start bluetooth
jan. 20 15:16:56 Zirum-Yoga-920-13IKB sudo[4630]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
jan. 20 15:16:56 Zirum-Yoga-920-13IKB systemd[1]: Starting Bluetooth service...
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Bluetooth daemon 5.64
jan. 20 15:16:56 Zirum-Yoga-920-13IKB systemd[1]: Started Bluetooth service.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Starting SDP server
jan. 20 15:16:56 Zirum-Yoga-920-13IKB sudo[4630]: pam_unix(sudo:session): session closed for user root
jan. 20 15:16:56 Zirum-Yoga-920-13IKB dbus-daemon[756]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.133' (uid=0 pid=4634 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Bluetooth management interface 1.22 initialized
jan. 20 15:16:56 Zirum-Yoga-920-13IKB systemd[1]: Starting Hostname Service...
jan. 20 15:16:56 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb142664a0 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb101a8050 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB pulseaudio[1814]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
jan. 20 15:16:56 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb1437dda0 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb14195ca0 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb14384310 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Too small Add Device complete event
jan. 20 15:16:56 Zirum-Yoga-920-13IKB bluetoothd[4634]: Too small Add Device complete event
jan. 20 15:16:56 Zirum-Yoga-920-13IKB dbus-daemon[756]: [system] Successfully activated service 'org.freedesktop.hostname1'
jan. 20 15:16:56 Zirum-Yoga-920-13IKB systemd[1]: Started Hostname Service.
jan. 20 15:17:01 Zirum-Yoga-920-13IKB CRON[4636]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
jan. 20 15:17:01 Zirum-Yoga-920-13IKB CRON[4637]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
# Result: Bluetooth inactive in systray

# Activating bluetooth from systray
jan. 20 15:17:18 Zirum-Yoga-920-13IKB NetworkManager[757]: <info>  [1737382638.0712] manager: (74:74:46:B4:E6:43): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/5)
jan. 20 15:17:18 Zirum-Yoga-920-13IKB NetworkManager[757]: <info>  [1737382638.0715] device (74:74:46:B4:E6:43): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
jan. 20 15:17:18 Zirum-Yoga-920-13IKB NetworkManager[757]: <info>  [1737382638.0720] device (74:74:46:B4:E6:43): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
jan. 20 15:17:18 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb11a685f0 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:17:18 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb125ffc50 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:17:18 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb125f1e50 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:17:18 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb11a881f0 StLabel.monospace:insensitive ("100%")] which is not in the stage.
jan. 20 15:17:18 Zirum-Yoga-920-13IKB gnome-shell[1922]: st_widget_get_theme_node called on the widget [0x64bb11aed180 StLabel.monospace:insensitive ("100%")] which is not in the stage.
# Bluetooth active and working.

Zirum · 20 January 2025 14:29

Thanks for the tip, checked it! Though, I dont have any bluetooth options in BIOS. Closest thing I have is "Always on USB", which is set to enabled.

Aravisian · 20 January 2025 16:34

Bluetooth is radio and therefor, falls under Wifi Drivers.

Drivers act as a communication bridge between the O.S. of the hardware and the User O.S.
If there is poor communication between the two, which your description suggests that there is, there may be an issue with the driver.

What model Wifi Card are you using and have you checked the driver?

Ponce-De-Leon · 20 January 2025 20:01

What @Aravisian wrote, is a Point. Could You take a Look at the ''Additional Drivers'' Tab in Software & Updates if there are any Drivers offered?

Zirum · 21 January 2025 09:08

Appreciate chipping in

My model is "Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter".
The driver seems to be "/sys/bus/pci/drivers/ath10k_pci/0000:6b:00.0"
So I tried checking for leads on driver page: About ath10k — Linux Wireless documentation

But unsure what to consider from here? Maybe some firmware update?

Also, I both grateful and in ave that you all actually spend time on digging down on what's in the end, a quite trivial problem. I hope you (as well as I) do it out of a desire that it does not help only me, but others from having the same problem in future (maybe even regardless computer or device)...

Zirum · 21 January 2025 09:15

Sorry, I missed to read this post before "processing" Aravisian's, thanks for the hint!

There are no additional drivers offered there currently.
No propriatary drivers in use (if its relevant)

zenzen · 21 January 2025 10:50

I just noticed this and found this (possibly) related thread that suggests disabling
power management in the kernel. Maybe is worth a try?

Zirum · 21 January 2025 11:56

While in the process of testing to turn that off, I noticed something that might be a good lead.

After boot, if I run only sudo systemctl start bluetooth, bluetooth does not start.

However, if I run rfkill unblock bluetooth followed by sudo systemctl start bluetooth, bluetooth starts.

I did not realize earlier that I should have attempted start after rfkill, sorry for that!

Seen some adding the command as startup script, which probably will work. But any inputs to why this happens?

If it matters, I have TLPUI installed, though Im unsure if it works on my laptop. I tried using it to test tpcie_aspm=off from other article.

zabadabadoo · 21 January 2025 13:40

Just as an aside. Are you dual-booting alongside Windows?
If true, in Windows Power Settings disable Fast Start-Up.
We have seen on occassion that setting sometimes creates issues with devices being grabbed/retained/controlled by Windows.

Zirum · 21 January 2025 14:05

Nope, no dual-booting.

What service "owns" the soft block/unblock, do you know? I find it a bit weird that although it seems like TLPUI offers a bunch of more or less related settings, I dont think its working as expected. So makes me wonder if I'm looking at unused or ignored config?

zabadabadoo · 21 January 2025 15:35

OK, it was just a thought. Thanks for confirming not dual-booting.

Out of interest, I did a websearch using searchterm :
"Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter no bluetooth on boot Ubuntu 22.04"
and found this: [SOLVED] Atheros Wifi Adapter Issue | Ubuntu 22.04 - Page 2
Have a look at post #12. Don't know if will help you or not.

Also.
The pcie error that you posted elsewhere, but zenzen quoted above in post #16 I think may be significant and worthy of further search and investigation.

jan. 20 15:14:13 Zirum-Yoga-920-13IKB kernel: ath10k_pci 0000:6b:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

I see you tried pcie_aspm=off
Was that from this AskUbuntu item with 48votes grub2 - PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) - Ask Ubuntu