Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 547571

Summary: [abrt] crash detected in arora-0.10.2-2.fc12
Product: [Fedora] Fedora Reporter: Steve Zakulec <spzakulec>
Component: aroraAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jreznik
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:9f5cfbc9def11b57eab8b1391a933a45e2eb23dc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-04 01:39:27 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 Steve Zakulec 2009-12-15 00:21:52 UTC
abrt 1.0.0 detected a crash.

Comment
-----
I had flashrom open  in another tab, but it definitely crashed after what I did below.
I was looking thru my gmail account, and had selected one of my mailing list subscriptions, and hit all, then select all conversations that match this.  I then hit Archive, and it crashed.

Attached file: backtrace
cmdline: /usr/bin/arora http://code.google.com/p/flashrom-live-cd/
component: arora
executable: /usr/bin/arora
kernel: 2.6.31.5-127.fc12.i686
package: arora-0.10.2-2.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Steve Zakulec 2009-12-15 00:21:54 UTC
Created attachment 378393 [details]
File: backtrace

Comment 2 Steve Zakulec 2009-12-15 00:31:37 UTC
It's definitely crashing each time I do the steps above- I select one of my daily mailings, (which has accumulated thousands of emails by now), and as soon as I press Archive on the whole lot, it crashes.

Comment 3 Jaroslav Reznik 2009-12-15 08:39:35 UTC
Thanks for reporting this issue. Looks like crash in QtNetwork code. This is an issue that needs to be addressed by the upstream developers as it's unfortunately really complex code. Probably to Arora developers as they can first check if they use it correctly.

Comment 4 Bug Zapper 2010-11-04 03:20:32 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 2010-12-04 01:39:27 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.