Bug 541574

Summary: Fatal error in gdk_x_error running /usr/share/virt-manager/virt-manager.py
Product: [Fedora] Fedora Reporter: Matthew Booth <mbooth>
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, dmalcolm, hbrock, ivazqueznet, james.antill, jforbes, jonathansteffan, katzj, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:9324cfee6d47253ca2aee83db72afcd69bf2d108
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-01 19:45:18 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 Matthew Booth 2009-11-26 11:51:31 UTC 
abrt detected a crash.

Comment: Using virt-manager.
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: python
executable: /usr/bin/python
kernel: 2.6.31.5-127.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 6
Comment 1 Matthew Booth 2009-11-26 11:51:35 UTC 
Created attachment 373980 [details]
File: backtrace
Comment 2 Dave Malcolm 2009-12-01 02:45:43 UTC 
Thank you for reporting this bug.

How reproducable is this problem?  If you run the program from a terminal, is an error message printed?

What version of virt-manager do you have installed?

Looking at the backtrace, it looks like a fatal error happened in frame 4 of the program's single thread inside gdk_x_error.

Reassigning component from "python" to "virt-manager"
Comment 3 Cole Robinson 2009-12-01 19:45:18 UTC 

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