RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:
gvfs-mtp-1.22.4-6.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/10
crash_function: sync_transfer_wait_for_completion
executable:     /usr/libexec/gvfsd-mtp
global_pid:     698
kernel:         3.10.0-327.4.5.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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
 #6 check_event
 #7 g_thread_proxy at /lib64/libglib-2.0.so.0

Created attachment 1128272 [details]
File: backtrace

Created attachment 1128273 [details]
File: cgroup

Created attachment 1128274 [details]
File: core_backtrace

Created attachment 1128275 [details]
File: dso_list

Created attachment 1128276 [details]
File: environ

Created attachment 1128277 [details]
File: exploitable

Created attachment 1128278 [details]
File: limits

Created attachment 1128279 [details]
File: machineid

Created attachment 1128280 [details]
File: maps

Created attachment 1128281 [details]
File: open_fds

Created attachment 1128282 [details]
File: proc_pid_status

Created attachment 1128283 [details]
File: var_log_messages

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:
https://bugzilla.gnome.org/show_bug.cgi?id=761278

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:
https://retrace.fedoraproject.org/faf/problems/2533841/

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.

https://access.redhat.com/errata/RHSA-2018:3140