Description of problem: Logged out then saw a message in journal of a crash. Version-Release number of selected component: bluez-5.56-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=536bbbdca4744da0a685bbf7d96e292d;i=5df1;b=00a1acc47b3148cd833ffd82d66e41c0;m=403defe53;t=5bce660c48ce0;x=9dfca1c061f107eb kernel: 5.11.3-50.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 #1 match_endpoint_by_path at profiles/audio/media.c:2188 #2 queue_remove_if at src/shared/queue.c:279 #3 proxy_removed_cb at profiles/audio/media.c:2210 #4 proxy_free at gdbus/client.c:568 #5 g_list_foreach at ../glib/glist.c:1090 #6 g_list_free_full at ../glib/glist.c:244 #7 service_disconnect at gdbus/client.c:1300 #8 service_filter at gdbus/watch.c:471 #9 message_filter at gdbus/watch.c:544
Created attachment 1761200 [details] File: backtrace
Created attachment 1761201 [details] File: core_backtrace
Created attachment 1761202 [details] File: cpuinfo
Created attachment 1761203 [details] File: dso_list
Created attachment 1761204 [details] File: environ
Created attachment 1761205 [details] File: exploitable
Created attachment 1761206 [details] File: limits
Created attachment 1761207 [details] File: maps
Created attachment 1761208 [details] File: mountinfo
Created attachment 1761209 [details] File: open_fds
Created attachment 1761210 [details] File: proc_pid_status
Created attachment 1761211 [details] File: var_log_messages
*** Bug 1941802 has been marked as a duplicate of this bug. ***
*** Bug 1947525 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I switched to a virtual console for approximately one minute. Once I returned from there to the graphical environment, ABRT notified me about this problem. reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=46433e4f0ece4cc099d9001d24e2ecd0;i=9c9e;b=92d4601f09ca4276beb294a9bf2cdc43;m=a679da6ed;t=5c122cb4f2a93;x=b5aed71f9d3aacae kernel: 5.11.15-300.fc34.x86_64 package: bluez-5.58-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Happened while entering password after opening laptop lid. reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=42afcc118102442ea3b1ea56177cb579;i=50e9ec;b=6262e999cba247beb7d8581bd2b99829;m=2d4bd19ff4;t=5c171335cf055;x=76aeec6a47c2e33 kernel: 5.11.12-300.fc34.x86_64 package: bluez-5.58-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1958671 has been marked as a duplicate of this bug. ***
*** Bug 1958752 has been marked as a duplicate of this bug. ***
*** Bug 1959529 has been marked as a duplicate of this bug. ***
*** Bug 1960050 has been marked as a duplicate of this bug. ***
*** Bug 1960311 has been marked as a duplicate of this bug. ***
*** Bug 1960369 has been marked as a duplicate of this bug. ***
*** Bug 1960861 has been marked as a duplicate of this bug. ***
*** Bug 1960992 has been marked as a duplicate of this bug. ***
*** Bug 1961154 has been marked as a duplicate of this bug. ***
Similar problem has been detected: ran yum update from GNOME; gnome crashed and lost all my open windows reporter: libreport-2.14.0 backtrace_rating: 3 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=eb84c1bc6c4848e89d4696a26071821f;i=f4c7;b=3db5d3fb1a2448c081433afd36ca4b59;m=5979472018;t=5c29d63d0ffd5;x=59b63f084962dfd9 kernel: 5.11.19-300.fc34.x86_64 package: bluez-5.58-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Closed all windows and logged out. Then logged back in as the same user. reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=7a2914c3184840e398ac76d264416696;i=130f;b=b0aed424c5a0415cbe46e82e2dd41291;m=78028ec45;t=5c1663ec735d8;x=4fdec942805f0cfa kernel: 5.11.16-300.fc34.x86_64 package: bluez-5.58-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1963933 has been marked as a duplicate of this bug. ***
*** Bug 1964564 has been marked as a duplicate of this bug. ***
*** Bug 1971221 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happened when waking the device from sleep reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=2a0137f1d10d403f87ab726bbfe1d706;i=dba;b=f7fe68774d004e99852e0d8fca3b071e;m=12b9df928;t=5c49baef10ea0;x=e011cbfc4500fdca kernel: 5.12.9-300.fc34.x86_64 package: bluez-5.58-2.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1901255 has been marked as a duplicate of this bug. ***
*** Bug 1941135 has been marked as a duplicate of this bug. ***
strcmp crashes here: => 0x00007fb7bd99eeee <+30>: vmovdqu (%rdi),%ymm1 Register value: rdi 0x0 0 So it looks like strcmp was called with a null pointer.
Similar problem has been detected: I logged out of my machine and then logged back in. It was sleeping previously. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=9e8e188e6fac4b998cb8a7af8670a331;i=1b1627;b=20267574ed944e2a836ba322c1ef0973;m=565764c9;t=5c2ccd71218a4;x=55bff500f71b670c kernel: 5.11.20-300.fc34.x86_64 package: bluez-5.58-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Left the computer unattended (but active, no standby, no hibernation) for some hours. I am using a bluetooth mouse and keyboard. Once I got back, the session broke and I had to unlock it from the virtual console. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/bluetooth.service cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: __strcmp_avx2 executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=e8ae646a85da4e81a5befdee35ae1fec;i=f843;b=f83d094ccee24ad093faae1e53712742;m=dd8db8fe4;t=5c58a610f4ab4;x=4e741ad63b23373f kernel: 5.12.11-300.fc34.x86_64 package: bluez-5.59-1.fc34 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1977487 has been marked as a duplicate of this bug. ***
Is there any development to tackle to the problem? Will there be any fix to this? Any workaround?
*** Bug 1979056 has been marked as a duplicate of this bug. ***
*** Bug 1980669 has been marked as a duplicate of this bug. ***
*** Bug 1981148 has been marked as a duplicate of this bug. ***
*** Bug 1985883 has been marked as a duplicate of this bug. ***
*** Bug 1988791 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.