Red Hat Bugzilla – Bug 554028
[abrt] crash in virt-manager-0.8.2-1.fc12
Last modified: 2010-03-06 08:45:30 EST
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
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
reason: Process was terminated by signal 6 (Aborted)
Created attachment 382749 [details]
Oh, wow. As someone who cares about their spelling, I must correct myself:
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...
*** This bug has been marked as a duplicate of bug 540810 ***