Bug 1046929

Summary: [abrt] gvfs-mtp: g_mount_spec_get(): gvfsd-mtp killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Khalid El-dehairy <kdehairy>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alexl, bnocera, divi, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/932c20f1e6949ae8461bff1050384f4ea9936fec
Whiteboard: abrt_hash:73a6d5a47e36274717d39ffeee50e6529b91042a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:51:54 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Khalid El-dehairy 2013-12-27 13:10:48 UTC 
Version-Release number of selected component:
gvfs-mtp-1.18.3-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/9
crash_function: g_mount_spec_get
executable:     /usr/libexec/gvfsd-mtp
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 g_mount_spec_get at gmountspec.c:394
 #1 g_mount_spec_get_type at gmountspec.c:404
 #2 g_mount_spec_to_string at gmountspec.c:417
 #3 g_vfs_backend_add_auto_info at gvfsbackend.c:576
 #4 g_vfs_job_enumerate_add_info at gvfsjobenumerate.c:191
 #5 do_enumerate at gvfsbackendmtp.c:1145
 #6 g_vfs_job_run at gvfsjob.c:197
 #8 g_thread_proxy at gthread.c:798

Potential duplicate: bug 851125
Comment 1 Khalid El-dehairy 2013-12-27 13:10:55 UTC 
Created attachment 842307 [details]
File: backtrace
Comment 2 Khalid El-dehairy 2013-12-27 13:10:57 UTC 
Created attachment 842308 [details]
File: cgroup
Comment 3 Khalid El-dehairy 2013-12-27 13:11:01 UTC 
Created attachment 842309 [details]
File: core_backtrace
Comment 4 Khalid El-dehairy 2013-12-27 13:11:04 UTC 
Created attachment 842310 [details]
File: dso_list
Comment 5 Khalid El-dehairy 2013-12-27 13:11:06 UTC 
Created attachment 842311 [details]
File: environ
Comment 6 Khalid El-dehairy 2013-12-27 13:11:10 UTC 
Created attachment 842312 [details]
File: exploitable
Comment 7 Khalid El-dehairy 2013-12-27 13:11:12 UTC 
Created attachment 842313 [details]
File: limits
Comment 8 Khalid El-dehairy 2013-12-27 13:11:15 UTC 
Created attachment 842314 [details]
File: maps
Comment 9 Khalid El-dehairy 2013-12-27 13:11:18 UTC 
Created attachment 842315 [details]
File: open_fds
Comment 10 Khalid El-dehairy 2013-12-27 13:11:21 UTC 
Created attachment 842316 [details]
File: proc_pid_status
Comment 11 Khalid El-dehairy 2013-12-27 13:11:23 UTC 
Created attachment 842317 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 10:11:40 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 13 Fedora End Of Life 2015-06-29 13:51:54 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.