Bug 607243

Summary: [abrt] crash in gvfs-archive-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Nuno Anjos <anjos.nuno>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: alexl, bnocera, mrcee2, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4cacdda4998f716721f16681b6a310470ef24978
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:17:03 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 Nuno Anjos 2010-06-23 15:34:15 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive file=/home/nanjos/Projects/ScriptRunner/ScriptRunner.tar.gz
comment: try to open tar.gz file, double click didn't work, open with shows 2 links to archive manager, one with icon another with no icon, the no icon gives this error.
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-archive
global_uuid: 4cacdda4998f716721f16681b6a310470ef24978
kernel: 2.6.33.5-124.fc13.x86_64
package: gvfs-archive-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. try to open tar.gz file
2.
3.

Comment 1 Nuno Anjos 2010-06-23 15:34:20 UTC
Created attachment 426293 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:17:03 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:17:03 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #583258.

Sorry for the inconvenience.