Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74578 - [bluez] bluez 5.64-2 segfaults when connecting my headphones

Attached to Project: Arch Linux
Opened by Samuel Reddy (GamerTechUniverse) - Thursday, 28 April 2022, 07:24 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 21 May 2022, 19:15 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

When I connect to my headphones, it causes bluetoothd to segfault. Downgrading to bluez 5.61-1 fixes the issue.

Backtrace:


#0 0x00007f1a5e74634c in __pthread_kill_implementation () from /usr/lib/libc.so.6
#1 0x00007f1a5e6f94b8 in raise () from /usr/lib/libc.so.6
#2 0x00007f1a5e6e3534 in abort () from /usr/lib/libc.so.6
#3 0x00007f1a5e73a397 in __libc_message () from /usr/lib/libc.so.6
#4 0x00007f1a5e75033c in malloc_printerr () from /usr/lib/libc.so.6
#5 0x00007f1a5e75062c in munmap_chunk () from /usr/lib/libc.so.6
#6 0x00007f1a5e754c2a in free () from /usr/lib/libc.so.6
#7 0x000055ef16384d6c in queue_remove_all (destroy=0x0, user_data=0x0, function=0x0, queue=0x55ef174c54f0) at src/shared/queue.c:343
#8 queue_destroy (destroy=0x0, queue=0x55ef174c54f0) at src/shared/queue.c:60
#9 queue_destroy (queue=0x55ef174c54f0, destroy=0x0) at src/shared/queue.c:55
#10 0x000055ef162f87db in setup_free (s=0x55ef174c4b30) at profiles/audio/a2dp.c:217
#11 setup_unref (setup=0x55ef174c4b30) at profiles/audio/a2dp.c:236
#12 0x000055ef162fa378 in transport_cb (io=0x55ef174bed00, err=<optimized out>, user_data=0x55ef174c4b30) at profiles/audio/a2dp.c:2460
#13 0x000055ef16321592 in accept_cb (io=0x55ef174bed00, cond=<optimized out>, user_data=0x55ef17497530) at btio/btio.c:191
#14 0x00007f1a5ea51163 in g_main_dispatch (context=0x55ef1745b530) at ../glib/glib/gmain.c:3417
#15 g_main_context_dispatch (context=0x55ef1745b530) at ../glib/glib/gmain.c:4135
#16 0x00007f1a5eaa79e9 in g_main_context_iterate.constprop.0 (context=0x55ef1745b530, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4211
#17 0x00007f1a5ea506a3 in g_main_loop_run (loop=0x55ef1745c6e0) at ../glib/glib/gmain.c:4411
#18 0x000055ef162efffd in mainloop_run () at src/shared/mainloop-glib.c:66
#19 mainloop_run_with_signal (func=0x55ef163338a0 <signal_callback>, user_data=0x0) at src/shared/mainloop-notify.c:188
#20 main (argc=<optimized out>, argv=<optimized out>) at src/main.c:1257
This task depends upon

Comment by Andreas Radke (AndyRTR) - Thursday, 28 April 2022, 17:36 GMT
Please check/report it there: https://github.com/bluez/bluez/issues
Comment by Samuel Reddy (GamerTechUniverse) - Saturday, 30 April 2022, 22:42 GMT
Found a similar bug report on the upstream github:
https://github.com/bluez/bluez/issues/327

Loading...