Created attachment 2054825 [details]
File: proc_pid_status

Created attachment 2054826 [details]
File: maps

Created attachment 2054827 [details]
File: limits

Created attachment 2054828 [details]
File: environ

Created attachment 2054829 [details]
File: open_fds

Created attachment 2054830 [details]
File: mountinfo

Created attachment 2054831 [details]
File: os_info

Created attachment 2054832 [details]
File: cpuinfo

Created attachment 2054833 [details]
File: core_backtrace

Created attachment 2054834 [details]
File: dso_list

Created attachment 2054835 [details]
File: backtrace

Created attachment 2060539 [details]
Relevant Information

This appears to be an upstream problem, per https://issuetracker.google.com/issues/327026299#comment5. Should this be closed as UPSTREAM?

I ran `adb devices`.


reporter:       libreport-2.17.15
type:           CCpp
reason:         adb killed by SIGABRT
journald_cursor: s=84853a78e66f4c5cbae74210c51ce2b6;i=9f6d06;b=3ec2a1f8f21c49b59085fa0d30ede555;m=93206bd;t=6287523139ed4;x=932c6c72d288d54e
executable:     /usr/bin/adb
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/snap.powershell.powershell-49b67a1a-1c81-492b-bcc6-861799a66097.scope
rootdir:        /
uid:            1000
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: libusb_submit_transfer
comment:        I ran `adb devices`.

Per [a comment in the upstream issue tracker][1], the solution is to invoke `adb` as the superuser.

[1]: https://issuetracker.google.com/issues/327026299#comment27:~:text=It%20appears%20so.-,Running%20the%20container%20in%20privileged%20mode%20makes%20ADB%20work%20even%20with%20LibUSB,-You%20seem%20to

Ran `adb devices`


reporter:       libreport-2.17.15
rootdir:        /
executable:     /usr/bin/adb
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-eef2819c-540a-4d87-92d3-0c813ae6b5a3.scope
journald_cursor: s=6b102c5b0a334757b3fed410c95192f6;i=17753d09;b=f9fb4550b71a48bd853d52e8d24c2b48;m=3fa35bca3a;t=62aa9a891fd6c;x=68d160497ac6e14f
package:        android-tools-1:35.0.1-2.fc41
uid:            1001
runlevel:       N 5
crash_function: libusb_submit_transfer
comment:        Ran `adb devices`
backtrace_rating: 4
type:           CCpp
kernel:         6.11.6-300.fc41.x86_64
reason:         adb killed by SIGABRT

*** Bug 2312531 has been marked as a duplicate of this bug. ***

(In reply to Mr. Beedell, Roke Julian Lockhart from comment #15)
> Per [a comment in the upstream issue tracker][1], the solution is to invoke
> `adb` as the superuser.
> 
> [1]:
> https://issuetracker.google.com/issues/327026299#comment27:~:
> text=It%20appears%20so.-,
> Running%20the%20container%20in%20privileged%20mode%20makes%20ADB%20work%20eve
> n%20with%20LibUSB,-You%20seem%20to

I'm not sure that is the same, at least for me I am not running in a container and I see the crash even if I run under sudo.

(In reply to Peter Robinson from comment #19)
> I'm not sure that is the same, at least for me I am not running in a
> container and I see the crash even if I run under sudo.

I'm not running it in a container either, although it definitely works for me with superuser elevation. However, I've been utilizing `su`. Perhaps try that method instead of `sudo`?

I think this bug is the issue:
https://issuetracker.google.com/issues/341439962#comment3

Apparently libusb support is new, you can work around with with an env var eg: "ADB_LIBUSB=0 adb devices -l"

It should be fixed in 35.0.3, although not sure when that's due: https://github.com/nmeum/android-tools/issues/153

> I'm not running it in a container either, although it definitely works for
> me with superuser elevation. However, I've been utilizing `su`. Perhaps try
> that method instead of `sudo`?

Doesn't work for me even as root proper, the "ADB_LIBUSB=0 adb devices" does work for me though.

I connected a Fairphone 5.


reporter:       libreport-2.17.15
type:           CCpp
reason:         adb killed by SIGABRT
journald_cursor: s=46bb43f1faea498db084fdfcb024f166;i=113ab4;b=b6011f24f24442768d16ad9330239124;m=1aff7816f;t=630e2a1e3523a;x=ef2867668b2c5cec
executable:     /usr/bin/adb
cmdline:        adb -L tcp:5037 fork-server server --reply-fd 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-dev.warp.Warp
rootdir:        /
uid:            1000
kernel:         6.13.7-200.fc41.x86_64
package:        android-tools-1:35.0.2-2.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: libusb_submit_transfer
comment:        I connected a Fairphone 5.

Created attachment 2081361 [details]
Coloured GDB BT Screenshot

(In reply to Mr. Beedell, Jared Richard William from comment #23)  
> I connected a Fairphone 5.

Is the undermentioned an example of this? It didn't appear in GNOME Abrt:

> ~~~log
> Core was generated by `/home/RokeJulianLockhart/.cache/mozilla/firefox/iauorfww.snrxu8/adb/adb -L tcp:5037 fork-server server --reply-fd 4'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x00005589d66d81af in libusb_submit_transfer ()
> [Current thread is 1 (Thread 0x7fd72bd507c0 (LWP 194707))]
> (gdb) bt
> #0  0x00005589d66d81af in libusb_submit_transfer ()
> #1  0x00005589d642b628 in LibusbConnection::SubmitWrite(Block&&) ()
> #2  0x00005589d642ad72 in LibusbConnection::Write(std::__1::unique_ptr<apacket, std::__1::default_delete<apacket> >) ()
> #3  0x00005589d6414f4f in atransport::Write(apacket*) ()
> #4  0x00005589d6414d4b in send_packet(apacket*, atransport*) ()
> #5  0x00005589d63fbf4c in send_connect(atransport*) ()
> #6  0x00005589d641e026 in ?? ()
> #7  0x00005589d640736b in fdevent_context::FlushRunQueue() ()
> #8  0x00005589d6442ab0 in fdevent_context_epoll::Loop() ()
> #9  0x00005589d639383e in adb_server_main(int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, char const*, int) ()
> #10 0x00005589d637eef9 in adb_commandline(int, char const**) ()
> #11 0x00007fd72bd56248 in __libc_start_call_main (main=main@entry=0x5589d6393d90 <main>, argc=argc@entry=7, argv=argv@entry=0x7ffd6cf96528) at ../sysdeps/nptl/libc_start_call_main.h:58
> #12 0x00007fd72bd5630b in __libc_start_main_impl (main=0x5589d6393d90 <main>, argc=7, argv=0x7ffd6cf96528, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd6cf96518) at ../csu/libc-start.c:360
> #13 0x00005589d6379469 in _start ()
> ~~~

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.

(In reply to Adam Williamson from comment #25)

I've not seen this for some time, per https://issuetracker.google.com/issues/327026299#comment28. Can anyone else confirm?

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.