Bug 622902

Summary: [abrt] virt-manager: _Xerror crash
Product: [Fedora] Fedora Reporter: Ferry Huberts <mailings>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED WORKSFORME 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:f410cdcc98541dc7426b59c4ef6a6f800bdb9e52
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-27 15:29:50 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 Ferry Huberts 2010-08-10 18:19:29 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
crash_function: raise
executable: /usr/bin/python
global_uuid: f410cdcc98541dc7426b59c4ef6a6f800bdb9e52
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: virt-manager-0.8.4-2.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.it crashed right after I created a qcow2 image for a new VM
2.
3.
Comment 1 Ferry Huberts 2010-08-10 18:19:42 UTC 
Created attachment 437964 [details]
File: backtrace
Comment 2 Cole Robinson 2010-08-21 22:16:30 UTC 
Is this reliably reproducible? If so, can you run virt-manager with the --sync option, it should help track this down.
Comment 3 Ferry Huberts 2010-10-25 07:14:00 UTC 
not reproducable.
tried it a few times but could not crash it anymore
sorry :-(
Comment 4 Cole Robinson 2010-10-27 15:29:50 UTC 
Thanks, closing as WORKSFORME