Bug 655182

Summary: [abrt] gvfs-archive-1.4.3-7.fc12: raise: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Suawomirr <slawomir.iwanek>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alexl, bnocera, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1611452760bd4e48e2a3ce7626b8544055c72455
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 12:00:09 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 Suawomirr 2010-11-19 19:50:19 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive 'file=/media/IMATION/cisco/materialy projektowe.iso'
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-archive
kernel: 2.6.32.23-170.fc12.i686.PAE
package: gvfs-archive-1.4.3-7.fc12
rating: 4
reason: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
time: 1290199142
uid: 500

How to reproduce
-----
1. tried to open an iso file to check what is in this archive
2.
3.
Comment 1 Suawomirr 2010-11-19 19:50:22 UTC 
Created attachment 461639 [details]
File: backtrace
Comment 2 Bug Zapper 2010-12-03 12:00:09 UTC 
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Thank you for reporting this bug and we are sorry it could not be fixed.