Description of problem: Tried to launch http://fedorapeople.org/groups/qa/testday-20130418-x86_64.iso Version-Release number of selected component: virt-manager-0.9.5-1.fc19 Additional info: backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: spice_logv executable: /usr/bin/python2.7 kernel: 3.9.0-0.rc6.git2.1.fc19.x86_64 runlevel: N 3 uid: 0 ureports_counter: 1 var_log_messages: Apr 18 19:55:59 dhcp201-146 abrt[11623]: Saved core dump of pid 11199 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-04-18-19:55:57-11199 (385425408 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 spice_logv at log.c:109 #3 spice_log at log.c:123 #4 canvas_get_lz at ../spice-common/common/canvas_base.c:802 #5 canvas_get_image_internal at ../spice-common/common/canvas_base.c:1110 #6 canvas_get_image at ../spice-common/common/canvas_base.c:1285 #7 canvas_draw_copy at ../spice-common/common/canvas_base.c:2215 #8 display_handle_draw_copy at channel-display.c:1383 #9 spice_channel_recv_msg at spice-channel.c:1860 #10 spice_channel_iterate at spice-channel.c:2073 #11 spice_channel_coroutine at spice-channel.c:2304
Created attachment 737254 [details] File: backtrace
Created attachment 737255 [details] File: cgroup
Created attachment 737256 [details] File: core_backtrace
Created attachment 737257 [details] File: dso_list
Created attachment 737258 [details] File: environ
Created attachment 737259 [details] File: limits
Created attachment 737260 [details] File: maps
Created attachment 737261 [details] File: open_fds
Created attachment 737262 [details] File: proc_pid_status
I installed F19a and installed Virtualization on it. It has some testing guest for F19. So the F19a host has a F19a guests. I connected via 'ssh -Y' from a F17 host and launched virt-manager. I noticed it closes when i was using anaconda. Launching virt-viewer resuts in a core dumped. Launching a local virt-manager on F17 and connecting to the f19a qemu also makes it close. This happens when anaconda is running in graphical mode on the F19a guest (on F19a host). It does not happen when the guest is in text mode or kms without xorg. With xorg, after some activity, virt-manager closes generating the abrt. This started to happen with the last round of updates. Previously i was able to use and install F19a guest on F19a hosts.
Launching it also happens without any remote connection. Using KDE on F19a, virt-manager and virt-viewer behaves in the same way, The first one closes and the second core-dumps.
Looks like spice, reassigning. Spice folks, this has now been hit twice in short order on F19 and the alpha isn't even out yet, meaning its probably going to get a lot of dupes very quickly. If someone could poke at this I'd appreciate it. (side note: it's annoying that just about every spice crash seems to end in spice_logv, which makes the abrt bug title not all that useful for distinguishing crashes. Any way that can be avoided ? )
*** This bug has been marked as a duplicate of bug 928973 ***