Bug 577273

Summary: [abrt] crash in virt-manager-0.8.2-1.fc12: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Curtis Taylor <cjt>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:fae26d24833d8f203e0a9b77c8a20b2094cf800e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-05 16:10:12 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 Curtis Taylor 2010-03-26 15:44:02 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
executable: /usr/bin/python
kernel: 2.6.32.9-70.fc12.x86_64
package: virt-manager-0.8.2-1.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. virsh net-edit default  (just took out the stp and delay settings for the bridge)
2. virsh net-destroy default
3. virsh net-start default
4. Start a previously stopped WinXP guest.
Results: virt-manager crashes, but guest boots.
Expected Results: virt-manager doesn't crash and guest boots.

Comment 1 Curtis Taylor 2010-03-26 15:44:04 UTC
Created attachment 402872 [details]
File: backtrace

Comment 2 Cole Robinson 2010-04-05 16:10:12 UTC

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