Bug 544055

Summary: [abrt] crash detected in python-2.6.2-2.fc12
Product: [Fedora] Fedora Reporter: Michael Hagmann <michael.hagmann>
Component: pythonAssignee: Dave Malcolm <dmalcolm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ajsfedora, alex-kas, antifreeze2173, antonis.g5, ashish3536, bferguss, cristionciu, dmalcolm, eduard0.ec0, gryphon1962m, ivazqueznet, james.antill, johnmargaritopoulos, jonathansteffan, josergc, jouni.000, jschrode, kamirski, katzj, keith.hewitt, kenmatrix, mailto, mihanit, mikes, mrblack, nja.aimo, omarberroteranlkf, raflexras, remimasse, sameer.subscriptions, scmcarlos, skinnypup, slarnold, vadim, viking2000, xyzk, zhangyud
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:86fd4f0a84f7c1d22384deef87eae03ce5878c91
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-03 19:58:05 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 Michael Hagmann 2009-12-03 19:52:02 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Configureing a Virtual Maschine
2.
3.


Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: python
executable: /usr/bin/python
kernel: 2.6.31.6-145.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 3
reason: Process was terminated by signal 6

Comment 1 Michael Hagmann 2009-12-03 19:52:05 UTC
Created attachment 375891 [details]
File: backtrace

Comment 2 Dave Malcolm 2009-12-03 19:58:05 UTC
Thank you for the bug report. 

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 540810 ***

Comment 3 Dave Malcolm 2009-12-18 19:46:50 UTC
Looking at the history of this bug:
  https://bugzilla.redhat.com/show_activity.cgi?id=544055
I see lots of people have added themselves to the CC on this bug after it was closed as a duplicate of 540810.

Are you doing this manually, or is this something that ABRT is doing?  If the latter, what are you seeing?  (If so, it seems like a bug to me; perhaps ABRT should instead CC you on the "main" bug, rather than on a duplicate).

Comment 4 Joachim Schröder 2009-12-18 22:07:31 UTC
Dave,

I just let abrt do whatever it wanted to do :-)

abrt claimed that this problem had not been reported before, so I filled in all appropriate info.

I am surprised it did not create a new BZ but attached to an existing one. Looks like a bug, indeed.
jos

Comment 5 Dave Malcolm 2009-12-18 22:19:13 UTC
Joachim: thanks for the info!  I've filed bug 548871 against "abrt" to try to track down this behavior.

Comment 6 Michael Setzer II 2009-12-20 03:31:30 UTC
I get this abort when running yumex????
It goes thru normally, and then terminates with a segment fault.
Run the abrt, and it shows the python error, and takes a long time to do hte report, and the pop up windows come up as blank for a long time.

Did this on two machines now, and get the same segment faults when running yumex.

Comment 7 Dave Malcolm 2009-12-23 19:19:09 UTC
(In reply to comment #6)
> I get this abort when running yumex????
> It goes thru normally, and then terminates with a segment fault.
> Run the abrt, and it shows the python error, and takes a long time to do hte
> report, and the pop up windows come up as blank for a long time.
> 
> Did this on two machines now, and get the same segment faults when running
> yumex.  

Michael: the yumex issue is a different one, for which a fix is available. See bug 548849.  (That bug generates extremely large backtraces, which may cause  issues inside ABRT; however those issues appear to also be separate from this virt-manager bug).

Hope this is helpful