Bug 715533

Summary: [abrt] gvfs-1.4.3-9.el6: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV)
Product: Red Hat Enterprise Linux 6 Reporter: prashant ingale <pingale>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: jwest, tsmetana, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-25 19:37:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description prashant ingale 2011-06-23 08:48:48 UTC
Created attachment 506141 [details]
sosreport

Description of problem:
reason: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV)

Version-Release number of selected component (if applicable):

architecture: x86_64
component: gvfs
release: Red Hat Enterprise Linux Client release 6.0 (Santiago)
How reproducible:


Steps to Reproduce:
1.Went to Thrash Folder
2.Went to restore a deleted file
3.
  
Actual results:
gvfsd-trash is crashed

Expected results:
gvfsd-trash should not crashed
Additional info:

Comment 3 Tomáš Bžatek 2011-07-22 17:20:27 UTC
I don't see anything obvious from the backtrace. Assuming trashing and restoring works for ordinary files, can you please find out if this happens randomly or on specific files or mountpoints? Also, have there been any emblems set on that file?