Bug 1416078

Summary: [abrt] gvfs-mtp: do_sync_bulk_transfer(): gvfsd-mtp killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Nick H. <nck.s.hayes>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: alexl, kcchouette+fedora, nck.s.hayes, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1c0e6df9cb60ab62a477654032cbbd6f277cc1b9
Whiteboard: abrt_hash:99428ee0923b796d87bf639b88271ee5c9eac53d;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:46:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Nick H. 2017-01-24 14:21:11 UTC
Description of problem:
Not sure how to reproduce. I had my Android phone hooked up to my PC at the time though.

Version-Release number of selected component:
gvfs-mtp-1.30.3-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.18 /org/gtk/gvfs/exec_spaw/0
crash_function: do_sync_bulk_transfer
executable:     /usr/libexec/gvfsd-mtp
global_pid:     1740
kernel:         4.9.3-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 do_sync_bulk_transfer at sync.c:174
 #1 libusb_bulk_transfer at sync.c:273
 #2 ptp_usb_event at libusb1-glue.c:1592
 #3 ptp_usb_event_wait at libusb1-glue.c:1651
 #4 LIBMTP_Read_Event at libmtp.c:2164
 #5 check_event at gvfsbackendmtp.c:677
 #6 g_thread_proxy at gthread.c:784

Potential duplicate: bug 1353187

Comment 1 Nick H. 2017-01-24 14:21:15 UTC
Created attachment 1243924 [details]
File: backtrace

Comment 2 Nick H. 2017-01-24 14:21:16 UTC
Created attachment 1243925 [details]
File: cgroup

Comment 3 Nick H. 2017-01-24 14:21:17 UTC
Created attachment 1243926 [details]
File: core_backtrace

Comment 4 Nick H. 2017-01-24 14:21:18 UTC
Created attachment 1243927 [details]
File: dso_list

Comment 5 Nick H. 2017-01-24 14:21:19 UTC
Created attachment 1243928 [details]
File: environ

Comment 6 Nick H. 2017-01-24 14:21:20 UTC
Created attachment 1243929 [details]
File: exploitable

Comment 7 Nick H. 2017-01-24 14:21:21 UTC
Created attachment 1243930 [details]
File: limits

Comment 8 Nick H. 2017-01-24 14:21:22 UTC
Created attachment 1243931 [details]
File: maps

Comment 9 Nick H. 2017-01-24 14:21:23 UTC
Created attachment 1243932 [details]
File: mountinfo

Comment 10 Nick H. 2017-01-24 14:21:24 UTC
Created attachment 1243933 [details]
File: namespaces

Comment 11 Nick H. 2017-01-24 14:21:24 UTC
Created attachment 1243934 [details]
File: open_fds

Comment 12 Nick H. 2017-01-24 14:21:25 UTC
Created attachment 1243935 [details]
File: proc_pid_status

Comment 13 Nick H. 2017-01-24 14:21:26 UTC
Created attachment 1243936 [details]
File: var_log_messages

Comment 14 Ondrej Holy 2017-01-26 09:40:52 UTC
Thanks for your bug report!

Did you work with the MTP mount somehow? Did you run some applications which might also operate with MTP devices? Did you use something else than Gvfs in order to mount MTP devices?

Comment 15 Nick H. 2017-01-26 14:30:51 UTC
I was only using Nautilus. If I remember correctly, accessing the mount hangs sometimes and you have to replug the phone to be able to transfer. That might have caused the crash... Not a big deal for me personally, but if it happens again I'll gather more data for this report.

Used Nautilus, bug is very rare and almost impossible to reproduce. (as far as I know)

Comment 16 Jeremy 2017-05-16 22:38:08 UTC
*** Bug 1451520 has been marked as a duplicate of this bug. ***

Comment 17 Fedora End Of Life 2017-11-16 14:44:37 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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'
of '25'.

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 25 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.

Comment 18 Fedora End Of Life 2017-12-12 10:46:52 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.