Is there a specific log for bluetooth?

Support
,
1

I listen to my podcasts through my desktop, there is a specific episode that kills the bluetooth service. I thought it was something to do with the name of the podcast, but other podcasts work that have the same special characters in the name. journalctl returns this -

Dec 02 09:35:59 HOSTNAME audit[21365]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=21365 comm="bluetoothd" exe="/usr/lib/bluetooth/bluetoothd" sig=11 res=1
Dec 02 09:35:59 HOSTNAME kernel: bluetoothd[21365]: segfault at 90 ip 0000563afd649718 sp 00007ffd44b91f00 error 4 in bluetoothd[563afd634000+c9000]
Dec 02 09:35:59 HOSTNAME kernel: Code: fe ff ff 0f 1f 80 00 00 00 00 48 8b 38 e8 a0 b7 ff ff 48 8b 43 70 48 85 c0 75 ef 48 8b 83 80 00 00 00 48 85 c0 74 1a 0f 1f 00 <48> 8b 30 48 89 df e8 8d f9 ff ff 48 8b 83 80 00 00 00 48 85 c0 75
Dec 02 09:35:59 HOSTNAME kernel: audit: type=1701 audit(1670002559.331:2265): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=21365 comm="bluetoothd" exe="/usr/lib/bluetooth/bluetoothd" sig=11 res=1
Dec 02 09:35:59 HOSTNAME audit: BPF prog-id=87 op=LOAD
Dec 02 09:35:59 HOSTNAME audit: BPF prog-id=88 op=LOAD
Dec 02 09:35:59 HOSTNAME audit: BPF prog-id=89 op=LOAD
Dec 02 09:35:59 HOSTNAME kernel: audit: type=1334 audit(1670002559.341:2266): prog-id=87 op=LOAD
Dec 02 09:35:59 HOSTNAME kernel: audit: type=1334 audit(1670002559.341:2267): prog-id=88 op=LOAD
Dec 02 09:35:59 HOSTNAME kernel: audit: type=1334 audit(1670002559.341:2268): prog-id=89 op=LOAD
Dec 02 09:35:59 HOSTNAME systemd[1]: Started Process Core Dump (PID 21398/UID 0).
Dec 02 09:35:59 HOSTNAME audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-coredump@5-21398-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 09:35:59 HOSTNAME kernel: audit: type=1130 audit(1670002559.345:2269): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-coredump@5-21398-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 09:35:59 HOSTNAME systemd-coredump[21399]: [🡕] Process 21365 (bluetoothd) of user 0 dumped core.
                                                       
                                                       Module linux-vdso.so.1 with build-id 90ee25c0c8a737fbd9ab0ab726544e975f60d2f0
                                                       Module libgpg-error.so.0 with build-id 470d76ceb1e53cb017f78c08936e9bafaeb4058b
                                                       Module libgcc_s.so.1 with build-id 85db482c4585a328d95ec41124337a967bb24d8f
                                                       Module liblz4.so.1 with build-id 84ea95d811dad359e94e100ebe6a746294ffe8a7
                                                       Module libzstd.so.1 with build-id ab54c2881f53ab314e134f3e08c76d504376dd5d
                                                       Module liblzma.so.5 with build-id 8a7334fec02fef6a82ff641a68b3e3200a44a702
                                                       Module libgcrypt.so.20 with build-id 8bf3cb884124273640de797a3e77d86c98434ea4
                                                       Module libcap.so.2 with build-id 9b38b08de708f439a9d0a4f8b9914151bc8d4b50
                                                       Module ld-linux-x86-64.so.2 with build-id 22bd7a2c03d8cfc05ef7092bfae5932223189bc1
                                                       Module libm.so.6 with build-id 2c8ff1d29b255da5b7371efd5caf57444d622838
                                                       Module libsystemd.so.0 with build-id 1c1489e575197ffbf417c79f926e572421f3692f
                                                       Module libpcre2-8.so.0 with build-id 917fc43d2c9f8539a3e324555c6c73886e8000a8
                                                       Module libc.so.6 with build-id 1e94beb079e278ac4f2c8bce1f53091548ea1584
                                                       Module libasound.so.2 with build-id d4458e121c818bcf170543dac0e12cfdadcf5b40
                                                       Module libdbus-1.so.3 with build-id 6d6e4846c8e56903b4fe7d992ae6bb30c8a20a9c
                                                       Module libglib-2.0.so.0 with build-id 49826f5cd4f784c8050176991d46fd93a5fcee9f
                                                       Module bluetoothd with build-id 1da3d38787dea67f8b9b4ebcf384a6cb7b07466f
                                                       Stack trace of thread 21365:
                                                       #0  0x0000563afd649718 n/a (bluetoothd + 0x36718)
                                                       #1  0x0000563afd649adc n/a (bluetoothd + 0x36adc)
                                                       #2  0x0000563afd6cc0ec n/a (bluetoothd + 0xb90ec)
                                                       #3  0x0000563afd6cc43b g_dbus_unregister_interface (bluetoothd + 0xb943b)
                                                       #4  0x0000563afd699a2b n/a (bluetoothd + 0x86a2b)
                                                       #5  0x00007f8ea18f6e90 g_slist_foreach (libglib-2.0.so.0 + 0x71e90)
                                                       #6  0x0000563afd6363ea n/a (bluetoothd + 0x233ea)
                                                       #7  0x0000563afd63518b n/a (bluetoothd + 0x2218b)
                                                       #8  0x00007f8ea1582290 n/a (libc.so.6 + 0x23290)
                                                       #9  0x00007f8ea158234a __libc_start_main (libc.so.6 + 0x2334a)
                                                       #10 0x0000563afd636025 n/a (bluetoothd + 0x23025)
                                                       ELF object binary architecture: AMD x86-64

I can’t really read coredumps, so I was hoping for something a bit more human readable. If anyone wants to try to duplicate the issue, I am using an Android phone, using podcast addict, and the episode was episode 047 of “A Problem Squared” - h t t p s://podcasts.apple.com/us/podcast/047-if-bees-flew-your-weight-and-honey-use-by-date/id1490290676?i=1000586895404 (Sorry for the copy/paste link, I can’t post them because i’m a new user).

Thanks in advance

2

I am not seeing a specific log for bluetooth, but I believe 6.1 of this wiki may be helpful, Bluetooth - ArchWiki

Once you get Bluetooth running with debugging, replicate your problem to see if anything helpful pops up in the terminal.

3

Did you try: :thinking:

journalctl --unit=bluetooth

And to aid you in starting that service with debugging enabled, you could use this command to create a “drop-in” config for that service:

sudo systemctl edit bluetooth

With this as new content for example:

[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/bluetoothd -d
1 Like