Bug 584474

Summary: [abrt] crash in virt-manager-0.8.3-3.fc13: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: drewskiwooskie
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:f5f61ffb4a4572943b01ef41b7120500eeefec0c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-27 16:28: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 drewskiwooskie 2010-04-21 16:15:28 UTC 
abrt 1.0.9 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
global_uuid: f5f61ffb4a4572943b01ef41b7120500eeefec0c
kernel: 2.6.33.2-57.fc13.x86_64
package: virt-manager-0.8.3-3.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Removed a virt IO Disk
2. Added a new hard disk
3. Started the VM
Comment 1 drewskiwooskie 2010-04-21 16:15:30 UTC 
Created attachment 408123 [details]
File: backtrace
Comment 2 drewskiwooskie 2010-04-22 12:37:59 UTC 
just the manager crashes, the virtual machines run just fine.
Comment 3 Cole Robinson 2010-04-27 16:28:05 UTC 

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