Version-Release number of selected component: gvfs-mtp-1.16.3-2.el7 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/5 crash_function: list_del executable: /usr/libexec/gvfsd-mtp kernel: 3.10.0-22.el7.x86_64 runlevel: N 5 type: CCpp uid: 1004 Truncated backtrace: Thread no. 1 (10 frames) #0 list_del at libusbi.h:119 #1 usbi_handle_transfer_completion at io.c:1460 #2 usbi_handle_disconnect at io.c:2448 #3 op_handle_events at os/linux_usbfs.c:2501 #4 handle_events at io.c:1941 #5 libusb_handle_events_timeout_completed at io.c:2021 #6 libusb_handle_events_completed at io.c:2120 #7 do_sync_bulk_transfer at sync.c:183 #8 libusb_bulk_transfer at sync.c:272 #9 ptp_usb_event at libusb1-glue.c:1557
Created attachment 800410 [details] File: backtrace
Created attachment 800411 [details] File: cgroup
Created attachment 800412 [details] File: core_backtrace
Created attachment 800414 [details] File: dso_list
Created attachment 800416 [details] File: environ
Created attachment 800417 [details] File: exploitable
Created attachment 800418 [details] File: limits
Created attachment 800419 [details] File: maps
Created attachment 800420 [details] File: open_fds
Created attachment 800421 [details] File: proc_pid_status
Created attachment 800422 [details] File: var_log_messages
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
I suppose you hard unplug the device without clean unmount, are you able to reproduce it? There is probably bug in libusb, because gvfs just waiting for LIBMTP_Read_Event, libmtp is also waiting for libusb_bulk_transfer, and libusb tries to remove entry from the list, because it received LIBUSB_TRANSFER_NO_DEVICE, however it caused SEGFAULT in Thread 1 (was the entry already removed?). Maybe there is some race with Thread 5, which is already using libusb, however it waits on mutex in time of crash...
It was done by clicking unmount in nautilus. I've tried the same in rebase 3.14 gnome and there is not problem. Will reopen if it occurs again.