Red Hat Bugzilla – Bug 544055
[abrt] crash detected in python-2.6.2-2.fc12
Last modified: 2010-01-06 10:47:50 EST
abrt 1.0.0 detected a crash.
How to reproduce
1. Configureing a Virtual Maschine
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
reason: Process was terminated by signal 6
Created attachment 375891 [details]
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 ***
Looking at the history of this bug:
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).
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.
Joachim: thanks for the info! I've filed bug 548871 against "abrt" to try to track down this behavior.
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.
(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
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