Description of problem:
Version-Release number of selected component:
cmdline: /usr/libexec/gvfsd-mtp --spawner :1.10 /org/gtk/gvfs/exec_spaw/23
runlevel: N 5
Thread no. 1 (10 frames)
#0 list_del at libusbi.h:137
#1 remove_from_flying_list at io.c:1447
#2 libusb_submit_transfer at io.c:1541
#3 do_sync_bulk_transfer at sync.c:185
#4 libusb_bulk_transfer at sync.c:273
#5 ptp_usb_event at libusb1-glue.c:1592
#6 ptp_usb_event_wait at libusb1-glue.c:1651
#7 LIBMTP_Read_Event at libmtp.c:2164
#8 check_event at gvfsbackendmtp.c:683
#9 g_thread_proxy at gthread.c:784
Created attachment 1248246 [details]
Created attachment 1248247 [details]
Created attachment 1248248 [details]
Created attachment 1248249 [details]
Created attachment 1248250 [details]
Created attachment 1248251 [details]
Created attachment 1248252 [details]
Created attachment 1248253 [details]
Created attachment 1248254 [details]
Created attachment 1248255 [details]
Created attachment 1248256 [details]
Created attachment 1248257 [details]
Created attachment 1248258 [details]
Thanks for your bug report.
Can you please provide some addition info what did you do when did it happen? Did you hard-unplug the device without unmounting, or during unmounting?
I cannot remember the steps to reproduce the bug. I can only tell that it happened during my mobile phone of Android 6.0 OS connected to Fedora rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
Same as bug #1512203 and bug #1538493?
Same as bug #1475468?
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.