Bug 639701

Summary: [abrt] file-roller-2.30.1.1-3.fc13: IA__gtk_propagate_event: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mat Booth <mat.booth>
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: alrikb, juniorroy, mclasen, sho.shimauchi, takhs20
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:8156e6404e707ad7981486c017f59b4a2ec10a07
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 12:02:17 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 Mat Booth 2010-10-03 14:01:33 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: file-roller file:///home/mbooth/workspace/eclipse/eclipse-3.6.0-src.tar.bz2
component: file-roller
crash_function: IA__gtk_propagate_event
executable: /usr/bin/file-roller
kernel: 2.6.34.7-56.fc13.x86_64
package: file-roller-2.30.1.1-3.fc13
rating: 4
reason: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: Was looking inside a bz2 archive, it's possible it was corrupt....
time: 1286114268
uid: 500

Comment 1 Mat Booth 2010-10-03 14:01:35 UTC
Created attachment 451274 [details]
File: backtrace

Comment 2 Roy 2010-10-06 14:00:27 UTC
Package: file-roller-2.30.1.1-3.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.download vim source
2.open in fileroller
3.

Comment 3 Karel Klíč 2010-11-08 18:54:44 UTC
*** Bug 605889 has been marked as a duplicate of this bug. ***

Comment 4 Karel Klíč 2010-11-08 18:54:48 UTC
*** Bug 608793 has been marked as a duplicate of this bug. ***

Comment 5 Karel Klíč 2010-11-08 18:54:53 UTC
*** Bug 614880 has been marked as a duplicate of this bug. ***

Comment 6 Karel Klíč 2010-11-08 18:54:57 UTC
*** Bug 627880 has been marked as a duplicate of this bug. ***

Comment 7 Bug Zapper 2011-05-31 12:04:12 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2011-06-28 12:02:17 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.