Bug 554028

Summary: [abrt] crash in virt-manager-0.8.2-1.fc12
Product: [Fedora] Fedora Reporter: Gideon Mayhak <gnafu_the_great>
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, error, hbrock, hgkamath, jforbes, metal3d, m_hur, peter.green, ravishankar.srinivasan, ros, twaugh, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4c30d6f07729d62435fdff24c1351603fb069046
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-26 16:52:49 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 Gideon Mayhak 2010-01-10 03:47:25 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. Go through New VM wizard to step 4/5
2. Select to Browse for "managed or existing storage"
3. Click New Volume and make a new disk
4. Try to click on that new disk

Comment
-----
When I clicked on it, it wasn't selected and my system locked up for a few seconds.  After about 30 seconds, virt-manager closed out completely and ABRT came up.

This has only happened once, and I've been able to complete the New VM wizard a few times now, but I still wanted to report this one occurance if it might help increase the stability of virt-manager!

Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
component: virt-manager
executable: /usr/bin/python
kernel: 2.6.31.9-174.fc12.x86_64
package: virt-manager-0.8.2-1.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
Comment 1 Gideon Mayhak 2010-01-10 03:47:28 UTC 
Created attachment 382749 [details]
File: backtrace
Comment 2 Gideon Mayhak 2010-01-10 03:50:29 UTC 
Oh, wow.  As someone who cares about their spelling, I must correct myself:

*occurrence
Comment 3 Tim Waugh 2010-01-25 17:39:50 UTC 
I've only seen it once too.  A tricky one to catch.

Often with gdk_x_error() crashes the advice is to run with --sync so that the errors are processed in synchronisation with the operations that caused them, giving more meaningful stack traces.

Unfortunately, virt-manager doesn't seem to like that option...
Comment 4 Cole Robinson 2010-01-26 16:52:49 UTC 

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