Description of problem: Keychron K14 went to sleep. Pressed a key to wake it up, the keyboard indicated it was connected but Fedora was not registering any keys. Bluetoothd crashed a few seconds later. Version-Release number of selected component: bluez-5.75-1.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: bluetoothd killed by SIGSEGV journald_cursor: s=5903d0671446456d995c10da180c3169;i=1dbbb2d;b=bd80effe6ecb422f81b44b95c94d2117;m=27d10ddb5;t=616b84aae5294;x=b1b5d2d8e810d9de executable: /usr/libexec/bluetooth/bluetoothd cmdline: /usr/libexec/bluetooth/bluetoothd cgroup: 0::/system.slice/bluetooth.service rootdir: / uid: 0 kernel: 6.8.7-300.fc40.x86_64 package: bluez-5.75-1.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: g_main_context_add_poll_unlocked comment: Keychron K14 went to sleep. Pressed a key to wake it up, the keyboard indicated it was connected but Fedora was not registering any keys. Bluetoothd crashed a few seconds later. Truncated backtrace: Thread no. 1 (6 frames) #0 g_main_context_add_poll_unlocked at ../glib/gmain.c:4628 #1 unblock_source at ../glib/gmain.c:3266 #3 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152 #4 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217 #6 mainloop_run at src/shared/mainloop-glib.c:66 #7 mainloop_run_with_signal at src/shared/mainloop-notify.c:188
Created attachment 2029880 [details] File: proc_pid_status
Created attachment 2029881 [details] File: maps
Created attachment 2029882 [details] File: limits
Created attachment 2029883 [details] File: environ
Created attachment 2029884 [details] File: open_fds
Created attachment 2029885 [details] File: mountinfo
Created attachment 2029886 [details] File: os_info
Created attachment 2029887 [details] File: cpuinfo
Created attachment 2029888 [details] File: core_backtrace
Created attachment 2029889 [details] File: exploitable
Created attachment 2029890 [details] File: dso_list
Created attachment 2029891 [details] File: var_log_messages
Created attachment 2029892 [details] File: backtrace
This issue stopped happening for a while but began occurring again with the Fedora 41 Beta. What can I do to provide a better backtrace to help resolve this issue? It's actively making my work difficult as Bluetooth keeps dying and I rely on Bluetooth peripherals to work. I did notice on F40 that, while Bluetooth did work, the quality of the connection got progressively worse and worse until I restarted bluez. Still using an AX210 chipset.
This crash also triggers a Wireplumber crash, see here: https://bugzilla.redhat.com/show_bug.cgi?id=2316221
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days