Bug 621084

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: Oleh Horbachov <gorbyo>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: alexl, bnocera, dcharlespyle, eblix08, faisalmm, mishu, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:18eba46ea7110eb84a0cb8b332c61768e7d8ca9d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 14:59:43 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 Oleh Horbachov 2010-08-04 08:20:57 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive 'file=/home/gorbyo/\xd0\x97\xd0\xb0\xd0\xb2\xd0\xb0\xd0\xbd\xd1\x82\xd0\xb0\xd0\xb6\xd0\xb5\xd0\xbd\xd0\xbd\xd1\x8f/Cloudy with a Chance of Meatballs.iso'
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-archive
global_uuid: 18eba46ea7110eb84a0cb8b332c61768e7d8ca9d
kernel: 2.6.33.6-147.2.4.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)

Comment 1 Oleh Horbachov 2010-08-04 08:21:00 UTC
Created attachment 436466 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 16:29:00 UTC
*** Bug 638817 has been marked as a duplicate of this bug. ***

Comment 3 Karel Klíč 2010-11-09 16:29:04 UTC
*** Bug 650175 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2011-06-01 12:08:50 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 5 Bug Zapper 2011-06-28 14:59:43 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.

Comment 6 D. Charles Pyle 2012-09-02 10:25:39 UTC
After updates over the last two days, I just had abrt report and try to re-open this bug. Since it was closed as a WONT-FIX due to end of life cycle, I can attest that this bug is now seen on my Fedora 17 machine after two days of updates. Regression, perhaps? Or, somthing else?

Comment 7 Mihai Harpau 2012-10-19 10:09:22 UTC
I also see this crash on my Fedora 17.

gvfs-archive 	1.12.3-1.fc17

Who can reopen this bug?