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)
Created attachment 382749 [details] File: backtrace
Oh, wow. As someone who cares about their spelling, I must correct myself: *occurrence
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 ***