Bug 661534

Summary: [abrt] gvfs-1.6.6-1.fc14: g_vfs_job_emit_finished: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: George <george>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: alexl, bnocera, david.richard.jeffery, denis.keller1, DerrikeG, dimanechepurenko, majhoul, ricardo.gladwell, tbzatek, tsmetana, xanexp
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:54356931f2ae03f39e845048380cf058bfb8800a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:22:33 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

Description George 2010-12-08 22:28:35 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-trash --spawner :1.9 /org/gtk/gvfs/exec_spaw/0
component: gvfs
crash_function: g_vfs_job_emit_finished
executable: /usr/libexec/gvfsd-trash
kernel: 2.6.35.9-64.fc14.i686.PAE
package: gvfs-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291666450
uid: 500

How to reproduce
-----
1.Just run the program it will show up.
2.
3.

Comment 1 George 2010-12-08 22:28:37 UTC
Created attachment 467594 [details]
File: backtrace

Comment 2 denis 2011-01-22 15:04:25 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.es war müll geoffnet
2.
3.


Comment
-----
nein

Comment 3 majhoul 2011-01-30 23:37:28 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. just opened the trash folder
2.
3.

Comment 4 Dave Jeffery 2011-02-01 12:40:03 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Sorry - I don't know.
2.
3.

Comment 5 Xane 2011-02-21 21:09:56 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
No idea

Comment
-----
N/A

Comment 6 dimanechepurenko 2011-03-11 21:37:10 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. try to restore data from trash
2.
3.

Comment 7 majhoul 2011-03-29 05:41:26 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. emptying the trash folder
2.
3.

Comment 8 denis 2011-04-01 19:11:33 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
weis nicht

Comment 9 ricardo.gladwell 2011-04-03 15:00:24 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Deleting the trash from a remote SMB file share

Comment 10 denis 2011-04-05 21:22:57 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
weis nicht

Comment 11 DerrikeG 2011-04-09 16:56:07 UTC
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Drag file into trash.
2. Open trash.
3. Close trash window. (Possibly before the file list had completely populated.)

Comment 12 abrt-bot 2012-03-20 15:22:33 UTC
Backtrace analysis found this bug to be similar to bug #768537, closing as duplicate.

Bugs which were found to be similar to this bug: bug #544327, bug #577131, bug #581069, bug #583462, bug #590750, bug #603608, bug #603739, bug #626672, bug #630189, bug #663528, bug #699346, bug #768537

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 768537 ***