Bug 2416721

Summary:

[abrt] android-tools: libusb_submit_transfer(): adb killed by SIGABRT

Product:

[Fedora] Fedora

Reporter:

Carlos Mogas da Silva <r3pek>

Component:

android-tools

Assignee:

Ivan Afonichev <ivan.afonichev>

Status:

NEW ---

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

high

Docs Contact:

Priority:

medium

Version:

CC:

admiller, epel-packagers-sig, go-sig, ivan.afonichev, jeroen, nathan95, priv.luk, r3pek

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

URL:

https://retrace.fedoraproject.org/faf/reports/bthash/31ed81ff1f32d40bb4ead1ccf5f6dfbdee0f86b

Whiteboard:

abrt_hash:26e7bbbb079cd272ccfec34bf527fc6fed5cae17;VARIANT_ID=kde;

Fixed In Version:

Doc Type:

---

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

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: maps	none
File: backtrace	none
File: proc_pid_status	none
File: limits	none
File: os_info	none
File: core_backtrace	none
File: cpuinfo	none
File: environ	none
File: dso_list	none
File: mountinfo	none
File: open_fds	none

Description Carlos Mogas da Silva 2025-11-24 09:36:41 UTC

Description of problem:
1. Install android-tools
2. plugin device with adb enabled
3. run "adb devices"

Version-Release number of selected component:
android-tools-1:35.0.2-10.fc43

Additional info:
reporter:       libreport-2.17.15
package:        android-tools-1:35.0.2-10.fc43
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
executable:     /usr/bin/adb
journald_cursor: s=2f1a28c2d71e4893bf90116e08acf1fa;i=27cfe2;b=d7bda4a57b494f9280d0796d6f21d6c6;m=74728c8f66;t=64453ddf22047;x=66ada7af95ff6d94
rootdir:        /
type:           CCpp
cgroup:         0::/user.slice/user-1598200003.slice/user/app.slice/app-org.kde.konsole
backtrace_rating: 4
runlevel:       /bin/sh: line 1: runlevel: command not found
uid:            1598200003
crash_function: libusb_submit_transfer
reason:         adb killed by SIGABRT
kernel:         6.17.7-300.fc43.x86_64

Truncated backtrace:
Thread no. 1 (21 frames)
 #6 libusb_submit_transfer at ../../libusb/io.c:1493
 #7 LibusbConnection::SubmitWrite at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/client/usb_libusb.cpp:318
 #8 LibusbConnection::Write at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/client/usb_libusb.cpp:342
 #9 atransport::Write at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/transport.cpp:1048
 #10 send_packet at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/transport.cpp:576
 #11 send_connect at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/adb.cpp:321
 #12 fdevent_register_transport at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/transport.cpp:767
 #13 operator() at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/transport.cpp:823
 #14 std::__invoke_impl<void, register_transport(atransport*)::<lambda()>&> at /usr/include/c++/15/bits/invoke.h:63
 #15 std::__invoke_r<void, register_transport(atransport*)::<lambda()>&> at /usr/include/c++/15/bits/invoke.h:113
 #16 std::_Function_handler<void(), register_transport(atransport*)::<lambda()> >::_M_invoke(const std::_Any_data &) at /usr/include/c++/15/bits/std_function.h:292
 #17 std::function<void()>::operator() at /usr/include/c++/15/bits/std_function.h:593
 #18 fdevent_context::FlushRunQueue at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/fdevent/fdevent.cpp:179
 #19 fdevent_context::HandleEvents at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/fdevent/fdevent.cpp:163
 #20 fdevent_context_epoll::Loop at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/fdevent/fdevent_epoll.cpp:189
 #21 fdevent_loop at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/fdevent/fdevent.cpp:259
 #22 adb_server_main at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/client/main.cpp:233
 #23 adb_commandline at /usr/src/debug/android-tools-35.0.2-10.fc43.x86_64/vendor/adb/client/commandline.cpp:1721
 #24 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58
 #25 __libc_start_main_impl at ../csu/libc-start.c:360
 #26 _start


Potential duplicate: bug 2312531

Comment 1 Carlos Mogas da Silva 2025-11-24 09:36:46 UTC

Created attachment 2116044 [details]
File: maps

Comment 2 Carlos Mogas da Silva 2025-11-24 09:36:47 UTC

Created attachment 2116045 [details]
File: backtrace

Comment 3 Carlos Mogas da Silva 2025-11-24 09:36:49 UTC

Created attachment 2116046 [details]
File: proc_pid_status

Comment 4 Carlos Mogas da Silva 2025-11-24 09:36:50 UTC

Created attachment 2116047 [details]
File: limits

Comment 5 Carlos Mogas da Silva 2025-11-24 09:36:51 UTC

Created attachment 2116048 [details]
File: os_info

Comment 6 Carlos Mogas da Silva 2025-11-24 09:36:52 UTC

Created attachment 2116049 [details]
File: core_backtrace

Comment 7 Carlos Mogas da Silva 2025-11-24 09:36:54 UTC

Created attachment 2116050 [details]
File: cpuinfo

Comment 8 Carlos Mogas da Silva 2025-11-24 09:36:55 UTC

Created attachment 2116051 [details]
File: environ

Comment 9 Carlos Mogas da Silva 2025-11-24 09:36:56 UTC

Created attachment 2116052 [details]
File: dso_list

Comment 10 Carlos Mogas da Silva 2025-11-24 09:36:58 UTC

Created attachment 2116053 [details]
File: mountinfo

Comment 11 Carlos Mogas da Silva 2025-11-24 09:36:59 UTC

Created attachment 2116054 [details]
File: open_fds

Comment 12 Carlos Mogas da Silva 2025-11-24 09:41:01 UTC

Just to add to the above, since it's a little "clearer"

❯ adb devices
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /tmp/adb.1598200003.log
Server had pid: 1020436
--- adb starting (pid 1020436) ---
11-24 09:35:13.160 1020436 1020436 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41
11-24 09:35:13.160 1020436 1020436 I adb     : main.cpp:63 Version 35.0.2-android-tools
11-24 09:35:13.160 1020436 1020436 I adb     : main.cpp:63 Installed as /usr/bin/adb
11-24 09:35:13.160 1020436 1020436 I adb     : main.cpp:63 Running on Linux 6.17.7-300.fc43.x86_64 (x86_64)
11-24 09:35:13.160 1020436 1020436 I adb     : main.cpp:63 
11-24 09:35:13.168 1020436 1020436 I adb     : auth.cpp:416 adb_auth_init...
11-24 09:35:13.168 1020436 1020436 I adb     : auth.cpp:152 loaded new key from '/home/r3pek/.android/adbkey' with fingerprint 192CADEA3523DE6676F2D2960EF7AE059D16A58D756BFDAF285023701B0EA70A
11-24 09:35:13.168 1020436 1020436 I adb     : auth.cpp:391 adb_auth_inotify_init...
11-24 09:35:14.168 1020436 1020436 E adb     : usb_libusb.cpp:602 failed to open device: Access denied (insufficient permissions)
11-24 09:35:14.168 1020436 1020436 I adb     : transport.cpp:1153 R5CT825F7XN: connection terminated: failed to open device: Access denied (insufficient permissions)
adb: ../../libusb/io.c:1493: libusb_submit_transfer: Assertion `transfer->dev_handle' failed.

Comment 13 Carlos Mogas da Silva 2025-11-24 09:44:39 UTC

Disregard, I know what happened. (might still be an issue though)

I had a VM started (using Virtual Machine manager) when I plugged in the android device, but it was auto taken to the vm. I then proceeded to unmap the usb device from the VM and back to the host. this is the state that actually produces this Insufficient Permissions problem.

You can close it if you want, or keep it open if you wanna debug this further.