Description of problem: Each time I use virt-manager to connect to distant hosts machines (outside my local network), when I close virt-manager, one of the theses 2 things may happen : . this signal killed (often when using Quit) or . python process remains running, using # 50% of CPU (this is the most probably ending) So I use to kill this process Actually I get an error when I connect to distant host, maybe this is related : Erreur lors de l'obtention de la connexion « qemu:///system » : erreur interne client socket is closed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 295, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in tick self._tick(noStatsUpdate) File "/usr/share/virt-manager/virtManager/connection.py", line 1320, in _tick self.hostinfo = self.vmm.getInfo() File "/usr/lib/python2.7/site-packages/libvirt.py", line 3346, in getInfo if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self) libvirtError: erreur interne client socket is closed Version-Release number of selected component: virt-manager-0.9.4-4.fc18 Additional info: backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: new_threadstate executable: /usr/bin/python2.7 kernel: 3.8.5-201.fc18.i686.PAE uid: 1000 ureports_counter: 1 xsession_errors: /usr/lib/python2.7/site-packages/gnome_abrt/application.py:62: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal Truncated backtrace: Thread no. 1 (10 frames) #0 new_threadstate at /usr/src/debug/Python-2.7.3/Python/pystate.c:200 #1 PyThreadState_New at /usr/src/debug/Python-2.7.3/Python/pystate.c:211 #2 PyGILState_Ensure at /usr/src/debug/Python-2.7.3/Python/pystate.c:598 #3 libvirt_virEventUpdateHandleFunc at libvirt-override.c:4634 #4 virEventUpdateHandle at util/event.c:70 #5 virNetSocketUpdateIOCallback at rpc/virnetsocket.c:1571 #6 virNetClientIOUpdateCallback at rpc/virnetclient.c:1645 #8 virNetClientIO at rpc/virnetclient.c:1799 #9 virNetClientSendInternal at rpc/virnetclient.c:1969 #10 virNetClientSendWithReply at rpc/virnetclient.c:1997
Created attachment 732680 [details] File: backtrace
Created attachment 732681 [details] File: cgroup
Created attachment 732682 [details] File: core_backtrace
Created attachment 732683 [details] File: dso_list
Created attachment 732684 [details] File: environ
Created attachment 732685 [details] File: limits
Created attachment 732686 [details] File: maps
Created attachment 732687 [details] File: open_fds
Created attachment 732688 [details] File: proc_pid_status
Created attachment 732689 [details] File: smolt_data
Created attachment 732690 [details] File: var_log_messages
*** Bug 877723 has been marked as a duplicate of this bug. ***
*** Bug 883310 has been marked as a duplicate of this bug. ***
i have only close the window with the x button on window's title bar backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: new_threadstate executable: /usr/bin/python2.7 kernel: 3.8.5-201.fc18.x86_64 package: virt-manager-0.9.4-4.fc18 reason: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors:
*** Bug 958270 has been marked as a duplicate of this bug. ***
F18 virt-manager is on a different version now adays, and given the general lack of dups for almost 4 months I'm going to assume this was fixed elsewhere in the stack, since it doesn't look like anything virt-manager is explicitly causing