Bug 715533 - [abrt] gvfs-1.4.3-9.el6: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-1.4.3-9.el6: Process /usr/libexec/gvfsd-trash was killed by signa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gvfs
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomáš Bžatek
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-23 08:48 UTC by prashant ingale
Modified: 2018-11-14 12:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 19:37:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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?
Note You need to log in before you can comment on or make changes to this bug.