Hello, I've encountered a possible bug when trying to connect my Bluetooth headset via A2DP. Pairing is fine, but when it tries to connect the bluetoothd segfaults, with the following stacktrace: #0 0x0000000000469d60 n/a (bluetoothd) #1 0x00000000004472d3 n/a (bluetoothd) #2 0x000000000047a31d n/a (bluetoothd) #3 0x0000000000447405 n/a (bluetoothd) #4 0x00007f8ac61cf45a g_main_context_dispatch (libglib-2.0.so.0) #5 0x00007f8ac61cf810 n/a (libglib-2.0.so.0) #6 0x00007f8ac61cfb32 g_main_loop_run (libglib-2.0.so.0) #7 0x000000000040b6b2 n/a (bluetoothd) #8 0x00007f8ac57a5511 __libc_start_main (libc.so.6) #9 0x000000000040bf0a n/a (bluetoothd) I've installed bluez via Arch Linux packages, and after downgrading to 5.43 the bug no longer appears. I recall seeing lots of work done between these two on A2DP, so I suspect a regression there. Relevant Arch bug, where they told me to hit here: https://bugs.archlinux.org/task/53442 Should I report it to your Bugzilla? Do you need any more info or help? -- Yours Faithfully, Cysioland https://cysioland.pl -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
