Version-Release number of selected component: virt-manager-1.1.0-4.git310f6527.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: spice_usb_device_manager_stop_event_listening executable: /usr/bin/python2.7 kernel: 3.17.7-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #0 spice_usb_device_manager_stop_event_listening at usb-device-manager.c:1228 #1 spice_usbredir_channel_disconnect_device at channel-usbredir.c:422 #2 spice_usbredir_channel_reset at channel-usbredir.c:121 #3 channel_disconnect at spice-channel.c:2646 #4 spice_channel_coroutine at spice-channel.c:2430 #5 coroutine_trampoline at coroutine_ucontext.c:63 #6 continuation_trampoline at continuation.c:55 #7 ?? at /lib64/libc.so.6 #8 ??
Created attachment 980104 [details] File: backtrace
Created attachment 980105 [details] File: cgroup
Created attachment 980106 [details] File: core_backtrace
Created attachment 980107 [details] File: dso_list
Created attachment 980108 [details] File: environ
Created attachment 980109 [details] File: exploitable
Created attachment 980110 [details] File: limits
Created attachment 980111 [details] File: maps
Created attachment 980112 [details] File: open_fds
Created attachment 980113 [details] File: proc_pid_status
Created attachment 980114 [details] File: var_log_messages
I have seen this triggered twice by the following sequence of events: Machine A exposes qemu virtual machine through ethernet with dynamic IP address. Machine B runs virt-manager and connects to machine A through IP. Machine B starts a VM on machine A through virt-manager and connects to its display. Machine A then refreshes DHCP lease and gets a *different* IP address. Machine B times out on connection to old IP address. virt-manager crashes on Machine B.
Another user experienced a similar problem: Initial reboot during graphical install of rhel 7.1, as a VM under f21. Both Virtual Machine Manager and the VM console windows died. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: spice_usb_device_manager_stop_event_listening executable: /usr/bin/python2.7 kernel: 3.18.7-200.fc21.x86_64 package: virt-manager-1.1.0-4.git310f6527.fc21 reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
faf reports almost 500 hits for this FWIW
(In reply to Cole Robinson from comment #14) > faf reports almost 500 hits for this FWIW most likely fixed by http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=e3932bfebbfec7637f3d03d90e8f9b75e3223236
*** Bug 1207626 has been marked as a duplicate of this bug. ***
*** Bug 1184259 has been marked as a duplicate of this bug. ***
spice-gtk-0.28-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/spice-gtk-0.28-2.fc22
spice-gtk-0.27-6.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/spice-gtk-0.27-6.fc21
Package phodav-2.0-1.fc22, spice-gtk-0.28-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing phodav-2.0-1.fc22 spice-gtk-0.28-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5433/phodav-2.0-1.fc22,spice-gtk-0.28-2.fc22 then log in and leave karma (feedback).
*** Bug 1211028 has been marked as a duplicate of this bug. ***
phodav-2.0-1.fc22, spice-gtk-0.28-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.