Bug 2330323

Summary: [abrt] android-tools: usbi_mutex_lock.part.0.lto_priv.3(): adb killed by SIGABRT
Product: [Fedora] Fedora Reporter: Cristian Ciupitu <cristian.ciupitu>
Component: android-toolsAssignee: Ivan Afonichev <ivan.afonichev>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 41CC: admiller, cristian.ciupitu, epel-packagers-sig, go-sig, ivan.afonichev, jeroen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4fce122bd0f1dd1d2e8d7bd85f5432bf4eaedce
Whiteboard: abrt_hash:67c051a91035dd7f82097df4ab6aae5ec328409d;VARIANT_ID=;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-16 17:56:57 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: dso_list
none
File: backtrace none

Description Cristian Ciupitu 2024-12-04 12:58:07 UTC 
Version-Release number of selected component:
android-tools-1:35.0.1-2.fc41

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         adb killed by SIGABRT
journald_cursor: s=b006d5bf0a184de4b7ec4d7ba95ec22e;i=1656ace;b=e7e4258062d44781b5f3f523bcf8ef65;m=257a2589f;t=6284ea0acf29b;x=d9f7302e24dd34e1
executable:     /usr/bin/adb
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
cgroup:         0::/user.slice/user-5000.slice/session-2.scope
rootdir:        /
uid:            5000
kernel:         6.11.10-300.fc41.x86_64
package:        android-tools-1:35.0.1-2.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: usbi_mutex_lock.part.0.lto_priv.3

Truncated backtrace:
Thread no. 1 (16 frames)
 #6 usbi_mutex_lock.part.0.lto_priv.3 at ../../libusb/os/threads_posix.h:46
 #7 usbi_mutex_lock at ../../libusb/os/linux_usbfs.c:2699
 #8 handle_iso_completion at ../../libusb/os/linux_usbfs.c:2492
 #9 reap_for_handle at ../../libusb/os/linux_usbfs.c:2688
 #10 op_handle_events at ../../libusb/os/linux_usbfs.c:2758
 #11 handle_events at ../../libusb/io.c:2283
 #12 libusb_handle_events_timeout_completed at ../../libusb/io.c:2370
 #13 libusb_handle_events at ../../libusb/io.c:2445
 #14 operator() at /usr/src/debug/android-tools-35.0.1-2.fc41.x86_64/vendor/adb/client/usb_libusb.cpp:1052
 #15 std::__invoke_impl<void, libusb::usb_init()::<lambda()> > at /usr/include/c++/14/bits/invoke.h:61
 #16 std::__invoke<libusb::usb_init()::<lambda()> > at /usr/include/c++/14/bits/invoke.h:96
 #17 std::thread::_Invoker<std::tuple<libusb::usb_init()::<lambda()> > >::_M_invoke<0> at /usr/include/c++/14/bits/std_thread.h:301
 #18 std::thread::_Invoker<std::tuple<libusb::usb_init()::<lambda()> > >::operator() at /usr/include/c++/14/bits/std_thread.h:308
 #19 std::thread::_State_impl<std::thread::_Invoker<std::tuple<libusb::usb_init()::<lambda()> > > >::_M_run(void) at /usr/include/c++/14/bits/std_thread.h:253
 #20 std::execute_native_thread_routine at ../../../../../libstdc++-v3/src/c++11/thread.cc:104
 #22 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78


Potential duplicate: bug 2317843
Comment 1 Cristian Ciupitu 2024-12-04 12:58:10 UTC 
Created attachment 2061093 [details]
File: proc_pid_status
Comment 2 Cristian Ciupitu 2024-12-04 12:58:12 UTC 
Created attachment 2061094 [details]
File: maps
Comment 3 Cristian Ciupitu 2024-12-04 12:58:13 UTC 
Created attachment 2061095 [details]
File: limits
Comment 4 Cristian Ciupitu 2024-12-04 12:58:14 UTC 
Created attachment 2061096 [details]
File: environ
Comment 5 Cristian Ciupitu 2024-12-04 12:58:15 UTC 
Created attachment 2061097 [details]
File: open_fds
Comment 6 Cristian Ciupitu 2024-12-04 12:58:17 UTC 
Created attachment 2061098 [details]
File: mountinfo
Comment 7 Cristian Ciupitu 2024-12-04 12:58:18 UTC 
Created attachment 2061099 [details]
File: os_info
Comment 8 Cristian Ciupitu 2024-12-04 12:58:19 UTC 
Created attachment 2061100 [details]
File: cpuinfo
Comment 9 Cristian Ciupitu 2024-12-04 12:58:20 UTC 
Created attachment 2061101 [details]
File: core_backtrace
Comment 10 Cristian Ciupitu 2024-12-04 12:58:21 UTC 
Created attachment 2061102 [details]
File: dso_list
Comment 11 Cristian Ciupitu 2024-12-04 12:58:23 UTC 
Created attachment 2061103 [details]
File: backtrace
Comment 12 Adam Williamson 2025-12-02 01:51:29 UTC 
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
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 '41'.

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 41 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 13 Samyak Jain (RedHat) 2025-12-16 17:56:57 UTC 
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 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.