Bug 971143

Summary: [abrt] gvfs-mtp-1.16.2-2.fc19: LIBMTP_Set_File_Name: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Milan Kerslager <milan.kerslager>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: alexl, bnocera, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:14e3c9526fdd01b1601854f9f7b63977a01b8654
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 15:28:17 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Milan Kerslager 2013-06-05 19:23:48 UTC
Description of problem:
I was trying to rename file on MTP device.

Version-Release number of selected component:
gvfs-mtp-1.16.2-2.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2
crash_function: LIBMTP_Set_File_Name
executable:     /usr/libexec/gvfsd-mtp
kernel:         3.9.4-301.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jun  5 21:18:36 velkej abrt[7222]: Saved core dump of pid 6395 (/usr/libexec/gvfsd-mtp) to /var/tmp/abrt/ccpp-2013-06-05-21:18:36-6395 (78471168 bytes)

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 LIBMTP_Set_File_Name at libmtp.c:6745
 #1 do_set_display_name at gvfsbackendmtp.c:1416
 #2 g_vfs_job_run at gvfsjob.c:197
 #4 g_thread_proxy at gthread.c:798

Comment 1 Milan Kerslager 2013-06-05 19:23:52 UTC
Created attachment 757345 [details]
File: backtrace

Comment 2 Milan Kerslager 2013-06-05 19:23:58 UTC
Created attachment 757346 [details]
File: cgroup

Comment 3 Milan Kerslager 2013-06-05 19:24:00 UTC
Created attachment 757347 [details]
File: core_backtrace

Comment 4 Milan Kerslager 2013-06-05 19:24:03 UTC
Created attachment 757348 [details]
File: dso_list

Comment 5 Milan Kerslager 2013-06-05 19:24:07 UTC
Created attachment 757349 [details]
File: environ

Comment 6 Milan Kerslager 2013-06-05 19:24:10 UTC
Created attachment 757350 [details]
File: limits

Comment 7 Milan Kerslager 2013-06-05 19:24:13 UTC
Created attachment 757351 [details]
File: maps

Comment 8 Milan Kerslager 2013-06-05 19:24:16 UTC
Created attachment 757352 [details]
File: open_fds

Comment 9 Milan Kerslager 2013-06-05 19:24:19 UTC
Created attachment 757353 [details]
File: proc_pid_status

Comment 10 Fedora End Of Life 2015-01-09 18:20:24 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 11 Fedora End Of Life 2015-02-17 15:28:17 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.