Bluetooth stops after waking up from sleep

General system Kernel, boot, graphics & hardware
1

Hello everyone,
my bluetooth stops working when my laptop wakes up after going to sleep.
I can’t even see the graphical option in my status bar to enable or disable the bluetooth

I get this error in my journal after waking up from sleep

Dec 02 15:57:38 endeavour kernel: Bluetooth: hci0: unexpected event for opcode 0x0c24
Dec 02 15:57:39 endeavour systemd-coredump[4669]: [🡕] Process 744 (bluetoothd) of user 0 dumped core.
                                                  
                                                  Stack trace of thread 744:
                                                  #0  0x00007fa5e472083c n/a (libc.so.6 + 0x8e83c)
                                                  #1  0x00007fa5e46d0668 raise (libc.so.6 + 0x3e668)
                                                  #2  0x00007fa5e46b84b8 abort (libc.so.6 + 0x264b8)
                                                  #3  0x00007fa5e4974044 n/a (libdbus-1.so.3 + 0xe044)
                                                  #4  0x00007fa5e499b8eb _dbus_warn_check_failed (libdbus-1.so.3 + 0x358eb)
                                                  #5  0x00007fa5e498a5f8 dbus_message_iter_append_basic (libdbus-1.so.3 + 0x245f8)
                                                  #6  0x0000558a116e904a n/a (bluetoothd + 0x6004a)
                                                  #7  0x0000558a11746289 n/a (bluetoothd + 0xbd289)
                                                  #8  0x0000558a1174ae3a n/a (bluetoothd + 0xc1e3a)
                                                  #9  0x0000558a1174aed4 n/a (bluetoothd + 0xc1ed4)
                                                  #10 0x00007fa5e4a314b0 g_slist_foreach (libglib-2.0.so.0 + 0x7a4b0)
                                                  #11 0x0000558a11746503 n/a (bluetoothd + 0xbd503)
                                                  #12 0x00007fa5e4a314b0 g_slist_foreach (libglib-2.0.so.0 + 0x7a4b0)
                                                  #13 0x0000558a1174652f n/a (bluetoothd + 0xbd52f)
                                                  #14 0x00007fa5e4a314b0 g_slist_foreach (libglib-2.0.so.0 + 0x7a4b0)
                                                  #15 0x0000558a1174652f n/a (bluetoothd + 0xbd52f)
                                                  #16 0x00007fa5e4a314b0 g_slist_foreach (libglib-2.0.so.0 + 0x7a4b0)
                                                  #17 0x0000558a11747d68 n/a (bluetoothd + 0xbed68)
                                                  #18 0x0000558a11747c89 n/a (bluetoothd + 0xbec89)
                                                  #19 0x00007fa5e497f663 dbus_connection_dispatch (libdbus-1.so.3 + 0x19663)
                                                  #20 0x0000558a11746b49 n/a (bluetoothd + 0xbdb49)
                                                  #21 0x00007fa5e4a10f69 n/a (libglib-2.0.so.0 + 0x59f69)
                                                  #22 0x00007fa5e4a6f327 n/a (libglib-2.0.so.0 + 0xb8327)
                                                  #23 0x00007fa5e4a11b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
                                                  #24 0x0000558a116ace62 n/a (bluetoothd + 0x23e62)
                                                  #25 0x00007fa5e46b9cd0 n/a (libc.so.6 + 0x27cd0)
                                                  #26 0x00007fa5e46b9d8a __libc_start_main (libc.so.6 + 0x27d8a)
                                                  #27 0x0000558a116adfc5 n/a (bluetoothd + 0x24fc5)
                                                  ELF object binary architecture: AMD x86-64
Dec 02 15:57:42 endeavour wpa_supplicant[862]: bgscan simple: Failed to enable signal strength monitoring

This started to occur during some update of the last month

I can restart bluetooth again either by restarting my laptop or by using :

systemctl restart bluetooth

But i want to know what is causing it to turn off and what is the permanent solution ?

2

The most likely explanation is a kernel update introduced a regression. If this is the case, the permanent solution will be for the bug to be fixed by the kernel devs. Probably one day it will just start working normally again after an update.

It is lucky you have a reliable workaround which is very easy to implement. You could probably just automate it without too much effort.

3

Yes I’ll wait for the update !