Bug 547608 - [abrt] crash detected in python-2.6.2-2.fc12
[abrt] crash detected in python-2.6.2-2.fc12
Product: Fedora
Classification: Fedora
Component: elisa (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthias Saou
Fedora Extras Quality Assurance
: 556357 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2009-12-15 01:08 EST by Craig Robson
Modified: 2010-12-03 20:39 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 20:39:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (79.83 KB, text/plain)
2009-12-15 01:08 EST, Craig Robson
no flags Details

  None (edit)
Description Craig Robson 2009-12-15 01:08:14 EST
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/elisa
component: python
executable: /usr/bin/python
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 Craig Robson 2009-12-15 01:08:16 EST
Created attachment 378432 [details]
File: backtrace
Comment 2 Dave Malcolm 2009-12-15 17:17:30 EST
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What version of elisa do you have installed?

Looking at the backtrace, it looks like the problem occurred in thread #1, but unfortunately that thread's frame data doesn't contain enough information to help track down what went wrong.

Reassigning component from "python" to "elisa"
Comment 3 Craig Robson 2009-12-15 23:01:35 EST
I'm running elisa-0.5.35-2.fc12.  This is often repeatable and seems to happen when I close Elisa by pressing the X in the upper right corner of Elisa.

All of the stack traces I get are the same.
Comment 4 Karel Klíč 2010-02-24 11:54:56 EST
*** Bug 556357 has been marked as a duplicate of this bug. ***
Comment 5 Jonathan 2010-03-20 18:59:59 EDT

How to reproduce
1. started elisa. 
2. updated elisa on the programs own suggestion
3. closed / crashed elisa
Comment 6 Jonathan 2010-03-21 05:36:37 EDT

How to reproduce
1. closed elisa
Comment 7 Bug Zapper 2010-11-03 23:19:27 EDT
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: 
Comment 8 Bug Zapper 2010-12-03 20:39:01 EST
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.

Note You need to log in before you can comment on or make changes to this bug.