Red Hat Bugzilla – Bug 1135546
[abrt] virt-manager: g_socket_constructed(): python2.7 killed by SIGTRAP
Last modified: 2015-04-11 22:42:23 EDT
Description of problem: At the conclusion of the install of Fedora 21 Server Alpha TC4 from the DVD ISO, I clicked the reboot button in Anaconda. As it started to reboot, virt-manager crashed. Version-Release number of selected component: virt-manager-1.0.1-3.fc21.1 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: g_socket_constructed executable: /usr/bin/python2.7 kernel: 3.16.1-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 13041 Truncated backtrace: Thread no. 1 (10 frames) #2 g_socket_constructed at /lib64/libgio-2.0.so.0 #3 g_object_new_internal at /lib64/libgobject-2.0.so.0 #4 g_object_new_valist at /lib64/libgobject-2.0.so.0 #5 g_initable_new_valist at /lib64/libgio-2.0.so.0 #6 g_initable_new at /lib64/libgio-2.0.so.0 #7 g_socket_new_from_fd at /lib64/libgio-2.0.so.0 #8 spice_channel_coroutine at /lib64/libspice-client-glib-2.0.so.8 #9 coroutine_trampoline at /lib64/libspice-client-glib-2.0.so.8 #10 continuation_trampoline at /lib64/libspice-client-glib-2.0.so.8 #11 ?? at /lib64/libc.so.6
Created attachment 932697 [details] File: backtrace
Created attachment 932698 [details] File: cgroup
Created attachment 932699 [details] File: core_backtrace
Created attachment 932700 [details] File: dso_list
Created attachment 932701 [details] File: environ
Created attachment 932703 [details] File: limits
Created attachment 932704 [details] File: maps
Created attachment 932705 [details] File: open_fds
Created attachment 932706 [details] File: proc_pid_status
Created attachment 932707 [details] File: var_log_messages
*** Bug 1135808 has been marked as a duplicate of this bug. ***
Still experiencing this issue pretty much whenever a guest machine reboots while I have a viewer open on it.
*** Bug 1049665 has been marked as a duplicate of this bug. ***
I tried to reproduce a bunch of times but couldn't make it stick. That said, there's a patch upstream now which sounds like it might fix this (I did my testing without the patch FWIW). I'll push a build with this patch and mark this bug fixed, but if it gathers any more abrt hits I'll reopen it. commit 5daee287d91080d24c4e7ae8a0eaf4e356331bae Author: Marc-André Lureau <marcandre.lureau@redhat.com> Date: Sun Nov 9 22:02:30 2014 +0100 tunnels: do not close unowned fd
virt-manager-1.1.0-4.git310f6527.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/virt-manager-1.1.0-4.git310f6527.fc21
Package virt-manager-1.1.0-4.git310f6527.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-1.1.0-4.git310f6527.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15270/virt-manager-1.1.0-4.git310f6527.fc21 then log in and leave karma (feedback).
Proposed as a Freeze Exception for 21-final by Fedora user sgallagh using the blocker tracking app because: This is an extremely common crash bug. It would reflect poorly on us to ship without this fix, if we can get sufficient karma in time for the release candidate.
(In reply to Fedora Blocker Bugs Application from comment #17) > Proposed as a Freeze Exception for 21-final by Fedora user sgallagh using > the blocker tracking app because: > > This is an extremely common crash bug. It would reflect poorly on us to > ship without this fix, if we can get sufficient karma in time for the > release candidate. I should note, I still haven't managed to reproduce this. So sgallagh (or anyone that can reliably reproduce), please let me know if the build fixes the issue
(In reply to Cole Robinson from comment #18) > (In reply to Fedora Blocker Bugs Application from comment #17) > > Proposed as a Freeze Exception for 21-final by Fedora user sgallagh using > > the blocker tracking app because: > > > > This is an extremely common crash bug. It would reflect poorly on us to > > ship without this fix, if we can get sufficient karma in time for the > > release candidate. > > I should note, I still haven't managed to reproduce this. So sgallagh (or > anyone that can reliably reproduce), please let me know if the build fixes > the issue I've been able to reproduce it consistently when using virt-manager to install Fedora 21 pre-releases remotely (via qemu+ssh://) on a RHEL 7.0 VM host. It consistently crashes when rebooting the installed system after anaconda completes. I'll attempt to verify this fix now.
Thanks. I wasn't testing with an ssh URI, maybe that was the issue
Discussed in 2014-11-19 blocker review meeting. virt-manager is a part of Server DVD, and it would great to have this crash fixed. It's not installed by default, so the change should be quite safe.
virt-manager-1.1.0-4.git310f6527.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Another user experienced a similar problem: AL intentar conectar a una instancia Libvirt en un centos7 remoto reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: g_socket_constructed executable: /usr/bin/python2.7 kernel: 3.17.7-300.fc21.x86_64 package: virt-manager-1.1.0-4.git310f6527.fc21 reason: python2.7 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Abrt thinks I just experienced bug 1135808, which is marked as a duplicate of this bug. I am using virt-manager 1.1.0.4.git310f6527.fc21.noarch.
I've just tripeed this again; f21 virt-manager-1.1.0-4.git310f6527.fc21.noarch
*** This bug has been marked as a duplicate of bug 1135808 ***