Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: spice_channel_recv_link_msg executable: /usr/bin/python2.7 kernel: 3.7.2-201.fc18.i686 remote_result: NOTFOUND uid: 1000 var_log_messages: Jan 19 19:50:17 tbr-desk-fc18 abrt[3983]: Saved core dump of pid 1774 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2013-01-19-19:50:14-1774 (373956608 bytes) Truncated backtrace: Thread no. 1 (6 frames) #0 spice_channel_recv_link_msg at spice-channel.c:1675 #1 spice_channel_coroutine at spice-channel.c:2299 #2 coroutine_trampoline at coroutine_ucontext.c:56 #3 continuation_trampoline at continuation.c:49 #4 makecontext at ../sysdeps/unix/sysv/linux/i386/makecontext.S:87 #5 ??
Created attachment 683188 [details] File: backtrace
Created attachment 683189 [details] File: cgroup
Created attachment 683190 [details] File: core_backtrace
Created attachment 683191 [details] File: dso_list
Created attachment 683192 [details] File: environ
Created attachment 683193 [details] File: limits
Created attachment 683194 [details] File: maps
Created attachment 683195 [details] File: open_fds
Created attachment 683196 [details] File: proc_pid_status
I just hit this crash when going from a full-screened VM back to a normal window. This SELinux violation came with it: type=AVC msg=audit(1361729857.879:6056): avc: denied { create } for pid=29170 comm="qemu-kvm" scontext=unconfined_u:system_r:svirt_t:s0:c305,c959 tcontext=unconfined_u:system_r:svirt_t:s0:c305,c959 tclass=rawip_socket type=SYSCALL msg=audit(1361729857.879:6056): arch=x86_64 syscall=socket success=no exit=EACCES a0=2 a1=80002 a2=1 a3=a8 items=0 ppid=1 pid=29170 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=2 tty=(none) comm=qemu-kvm exe=/usr/bin/qemu-kvm subj=unconfined_u:system_r:svirt_t:s0:c305,c959 key=(null)
*** Bug 929184 has been marked as a duplicate of this bug. ***
*** Bug 926881 has been marked as a duplicate of this bug. ***
Also got a hit from gnome-boxes, so moving to spice-gtk.
Usually crashes happen for me when a guest powers down which brings down the whole of virt-manager.
It occurred to me in 2 circumstances: a restart and a rescale.
I can hit this by opening and closing the VM guest window repeatedly in virt-manager. Generally somewhere between try 5 and 10 it takes down all of virt-manager.
It happened to me when I had finished installing a Debian 7 guest, on the last reboot, before the guest comes up again. When starting virt-manager again, this particular guest was down, but all others were unaffected.
This causes https://retrace.fedoraproject.org/faf/reports/87147/.
Any progress on this? This happens to me on every single guest powerdown or reboot.
Is there anything in the VM log when this happens? They are in /var/log/libvirt/qemu/logs/ What spice-gtk version are you using? Looking at the retrace/faf report, this may have been fixed in f19 (though I would have liked to get more detailed on the 4 f19 reports there to know if they are old or not).
Created attachment 758323 [details] Guest log. Shutdown triggered virt-manager crash.
Will any fix be backported to F18, or just use F19-preview?
I managed to reproduce with 0.15.3 in f19.
The crash occurs because of "incomplete link header", and c->peer_msg is NULL It is solved by the following commit in 0.19. commit b19acbca339a3a630f7f19e1fe5b7cc21fccd737 Author: Dunrong Huang <riegamaths> Date: Mon Mar 11 16:30:02 2013 +0800 spice-channel: Do not segfault fault if peer_msg was a NULL pointer $ remote-viewer spice://192.168.0.233:111 # 111 is not a valid spice port (remote-viewer:29381): GSpice-WARNING **: incomplete link header (-104/16) Segmentation fault (core dumped) I updated the f18 package, build follows soon
spice-gtk-0.18-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/spice-gtk-0.18-2.fc18
Package spice-gtk-0.18-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spice-gtk-0.18-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-11496/spice-gtk-0.18-2.fc18 then log in and leave karma (feedback).
spice-gtk-0.18-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.