Description of problem:
I am using mtp to connect to my Nexus 5 phone. Most of the time it works just fine. Not sure where this comes from.
Version-Release number of selected component:
cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/10
runlevel: N 5
Thread no. 1 (8 frames)
#0 sync_transfer_wait_for_completion at /lib64/libusb-1.0.so.0
#1 do_sync_bulk_transfer at /lib64/libusb-1.0.so.0
#2 libusb_bulk_transfer at /lib64/libusb-1.0.so.0
#3 ptp_usb_event at /lib64/libmtp.so.9
#4 ptp_usb_event_wait at /lib64/libmtp.so.9
#5 LIBMTP_Read_Event at /lib64/libmtp.so.9
#7 g_thread_proxy at /lib64/libglib-2.0.so.0
Created attachment 1128272 [details]
Created attachment 1128273 [details]
Created attachment 1128274 [details]
Created attachment 1128275 [details]
Created attachment 1128276 [details]
Created attachment 1128277 [details]
Created attachment 1128278 [details]
Created attachment 1128279 [details]
Created attachment 1128280 [details]
Created attachment 1128281 [details]
Created attachment 1128282 [details]
Created attachment 1128283 [details]
This is well know upstream bug, however it seems that we can't do much with it in gvfs. Probably some changes in libmtp are needed. See:
The upstream bug report contains several patches, which should fix this issue. The patches should be part of the planned rebase. Unfortunately, it requires unreleased libmtp version...
It seems that this is still happening in Fedora 26 regardless of fixes from: https://bugzilla.gnome.org/show_bug.cgi?id=761278 .
Hmm, it seems that there aren't any crashes in sync_transfer_wait_for_completion for Fedora 27, so the crashes for Fedora 26 happened probably before gvfs rebuilt against newer libmtp:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.