Bug 2278052

Summary: [abrt] bluez: queue_push_tail(): bluetoothd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Maxim Therrien <acerspyro>
Component: bluezAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: acerspyro, balkov, dwmw2, gopalkrishna.tiwari, nerijus, pbrobinson, spacewar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2dfcdb9b47b240bb9dcd1c7f5fbbb3777398076
Whiteboard: abrt_hash:61db4c996851d0e07246a719db980e9d0e39b359;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-05-16 08:14:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: var_log_messages
none
File: backtrace none

Description Maxim Therrien 2024-04-30 22:19:55 UTC
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=0b543f9f4ea94899b896c8b1535e3dde;i=1dc04b0;b=6c54aed2c16d4d5a88dc2fc7302f1833;m=6876c34e;t=616c604c0b860;x=8658d99429d03c02
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: queue_push_tail

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 queue_push_tail at /usr/include/bits/string_fortified.h:59
 #2 bt_uhid_record at src/shared/uhid.c:129
 #3 uhid_read_handler at src/shared/uhid.c:158
 #4 watch_callback at src/shared/io-glib.c:157
 #6 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152
 #7 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217
 #9 mainloop_run at src/shared/mainloop-glib.c:66
 #10 mainloop_run_with_signal at src/shared/mainloop-notify.c:188

Comment 1 Maxim Therrien 2024-04-30 22:19:58 UTC
Created attachment 2030401 [details]
File: proc_pid_status

Comment 2 Maxim Therrien 2024-04-30 22:20:00 UTC
Created attachment 2030402 [details]
File: maps

Comment 3 Maxim Therrien 2024-04-30 22:20:01 UTC
Created attachment 2030403 [details]
File: limits

Comment 4 Maxim Therrien 2024-04-30 22:20:03 UTC
Created attachment 2030404 [details]
File: environ

Comment 5 Maxim Therrien 2024-04-30 22:20:04 UTC
Created attachment 2030405 [details]
File: open_fds

Comment 6 Maxim Therrien 2024-04-30 22:20:06 UTC
Created attachment 2030406 [details]
File: mountinfo

Comment 7 Maxim Therrien 2024-04-30 22:20:07 UTC
Created attachment 2030407 [details]
File: os_info

Comment 8 Maxim Therrien 2024-04-30 22:20:09 UTC
Created attachment 2030408 [details]
File: cpuinfo

Comment 9 Maxim Therrien 2024-04-30 22:20:10 UTC
Created attachment 2030409 [details]
File: core_backtrace

Comment 10 Maxim Therrien 2024-04-30 22:20:12 UTC
Created attachment 2030410 [details]
File: exploitable

Comment 11 Maxim Therrien 2024-04-30 22:20:13 UTC
Created attachment 2030411 [details]
File: dso_list

Comment 12 Maxim Therrien 2024-04-30 22:20:14 UTC
Created attachment 2030412 [details]
File: var_log_messages

Comment 13 Maxim Therrien 2024-04-30 22:20:16 UTC
Created attachment 2030413 [details]
File: backtrace

Comment 14 Maxim Therrien 2024-05-02 22:02:52 UTC
Woke up Keychron K14s while audio was playing through Logi Vibe 100 headset. All bluetooth devices immediately disconnected and bluez crashed.


reporter:       libreport-2.17.15
type:           CCpp
reason:         bluetoothd killed by SIGSEGV
journald_cursor: s=0b543f9f4ea94899b896c8b1535e3dde;i=1dc04b0;b=6c54aed2c16d4d5a88dc2fc7302f1833;m=6876c34e;t=616c604c0b860;x=8658d99429d03c02
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: queue_push_tail
comment:        Woke up Keychron K14s while audio was playing through Logi Vibe 100 headset. All bluetooth devices immediately disconnected and bluez crashed.

Comment 15 Nerijus Baliūnas 2024-05-09 09:26:25 UTC
I connected headset.


reporter:       libreport-2.17.15
reason:         bluetoothd killed by SIGSEGV
type:           CCpp
runlevel:       N 5
rootdir:        /
uid:            0
crash_function: queue_push_tail
cmdline:        /usr/libexec/bluetooth/bluetoothd
executable:     /usr/libexec/bluetooth/bluetoothd
backtrace_rating: 4
kernel:         6.8.7-300.fc40.x86_64
comment:        I connected headset.
package:        bluez-5.75-1.fc40
cgroup:         0::/system.slice/bluetooth.service
journald_cursor: s=9db7c39712e94ceb82c44a783c0a20ff;i=327b4d4;b=0b5683030c49473f9ba788a5c89e666a;m=64d47adab9;t=6179cf039dedd;x=79e4c0593d81606a

Comment 16 Ben 2024-05-17 15:32:29 UTC
Using a Bluetooth keyboard with a timed low-power mode and any Bluetooth-connected audio devices of any kind.

When the keyboard returns to full power mode, all BT-connected audio devices are instantly disconnected (presumably the proximal cause is this sigsegv in bluetoothd). 


reporter:       libreport-2.17.15
type:           CCpp
reason:         bluetoothd killed by SIGSEGV
journald_cursor: s=49ebb9f8142a4718831daff5a3167cfd;i=e49d;b=725aedfac2874c8eaf2059dbe99e5fc3;m=144450ad1d;t=616368a822dc1;x=5993b39033fc1c9
executable:     /usr/libexec/bluetooth/bluetoothd
cmdline:        /usr/libexec/bluetooth/bluetoothd
cgroup:         0::/system.slice/bluetooth.service
rootdir:        /
uid:            0
kernel:         6.8.6-300.fc40.x86_64
package:        bluez-5.75-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: queue_push_tail

Comment 17 Aoife Moloney 2025-04-25 10:34:21 UTC
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.

Comment 18 Fedora Admin user for bugzilla script actions 2025-05-07 03:01:05 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 19 Fedora Admin user for bugzilla script actions 2025-05-07 16:28:53 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 20 Fedora Admin user for bugzilla script actions 2025-05-08 03:27:52 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 21 Aoife Moloney 2025-05-16 08:14:27 UTC
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.