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: _pygi_closure_handle executable: /usr/bin/python2.7 kernel: 3.17.0-0.rc0.git6.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _pygi_closure_handle at /usr/lib64/python2.7/site-packages/gi/_gi.so #1 ffi_closure_unix64_inner at /lib64/libffi.so.6 #2 ffi_closure_unix64 at /lib64/libffi.so.6 #3 gtk_cell_renderer_real_get_preferred_size at /lib64/libgtk-3.so.0 #4 gtk_cell_renderer_get_preferred_width at /lib64/libgtk-3.so.0 #5 gtk_cell_area_request_renderer at /lib64/libgtk-3.so.0 #6 compute_size at /lib64/libgtk-3.so.0 #7 gtk_cell_area_box_get_preferred_width at /lib64/libgtk-3.so.0 #8 gtk_tree_view_column_cell_get_size at /lib64/libgtk-3.so.0 #9 validate_row at /lib64/libgtk-3.so.0
Created attachment 927456 [details] File: backtrace
Created attachment 927457 [details] File: cgroup
Created attachment 927458 [details] File: core_backtrace
Created attachment 927459 [details] File: dso_list
Created attachment 927460 [details] File: environ
Created attachment 927461 [details] File: exploitable
Created attachment 927462 [details] File: limits
Created attachment 927463 [details] File: maps
Created attachment 927464 [details] File: open_fds
Created attachment 927465 [details] File: proc_pid_status
Created attachment 927466 [details] File: var_log_messages
Another user experienced a similar problem: Opened virt-manager (sudo virt-manager) which attempted to connect to a remote machine and my local qemu. Crash occurred sometime after I entered credentials for the remote machine. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: _pygi_closure_handle executable: /usr/bin/python2.7 kernel: 3.17.0-0.rc0.git7.1.fc22.x86_64 package: virt-manager-1.0.1-3.fc21.1 reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
*** Bug 1131233 has been marked as a duplicate of this bug. ***
Stack trace ends in pygobject3, and the reports all coincide with f21 update to pygobject3-3.13.4-1.fc21, which is listed in the faf reports. But f21 has a new pygobject3 version now, so I'll just close as CURRENTRELEASE and reopen if we get any more hits
virt-manager crashed even with new pygobject3 sh-4.3# rpm -qa virt-manager* pygobject3* virt-manager-1.0.1-3.fc21.1.noarch pygobject3-3.13.90-1.fc21.x86_64 pygobject3-base-3.13.90-1.fc21.x86_64 virt-manager-common-1.0.1-3.fc21.1.noarch Do you need any data from me?
Here are to 30 frames from back trace: #0 0x00007fa6ea8b8fc7 in _pygi_closure_handle () at /usr/lib64/python2.7/site-packages/gi/_gi.so #1 0x0000003d3d805b4f in ffi_closure_unix64_inner (closure=0x7fa6e9acb010, rvalue=0x7fff0398ea50, reg_args=0x7fff0398e9a0, argp=0x7fff0398ea78 "@bR\365\064") at ../src/x86/ffi64.c:670 #2 0x0000003d3d805ec8 in ffi_closure_unix64 () at ../src/x86/unix64.S:229 #3 0x00000034f552625e in gtk_cell_renderer_real_get_preferred_size () at /lib64/libgtk-3.so.0 #4 0x00000034f5527875 in gtk_cell_renderer_get_preferred_width () at /lib64/libgtk-3.so.0 #5 0x00000034f551f011 in gtk_cell_area_request_renderer () at /lib64/libgtk-3.so.0 #6 0x00000034f551f8f0 in compute_size () at /lib64/libgtk-3.so.0 #7 0x00000034f5520b28 in gtk_cell_area_box_get_preferred_width () at /lib64/libgtk-3.so.0 #8 0x00000034f574c97a in gtk_tree_view_column_cell_get_size () at /lib64/libgtk-3.so.0 #9 0x00000034f572ce3e in validate_row () at /lib64/libgtk-3.so.0 #10 0x00000034f5734267 in do_presize_handler () at /lib64/libgtk-3.so.0 #11 0x00000034f57349bc in presize_handler_callback () at /lib64/libgtk-3.so.0 #12 0x00000034f5762694 in gtk_widget_on_frame_clock_update () at /lib64/libgtk-3.so.0 #13 0x00000030a6210104 in _g_closure_invoke_va () at /lib64/libgobject-2.0.so.0 #14 0x00000030a622aaa0 in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #15 0x00000030a622b83a in g_signal_emit_by_name () at /lib64/libgobject-2.0.so.0 #16 0x00000034f502e8db in gdk_frame_clock_paint_idle () at /lib64/libgdk-3.so.0 #17 0x00000034f5020a18 in gdk_threads_dispatch () at /lib64/libgdk-3.so.0 #18 0x00000030a5a4a5d3 in g_timeout_dispatch () at /lib64/libglib-2.0.so.0 #19 0x00000030a5a49b6b in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #20 0x00000030a5a49f08 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #21 0x00000030a5a49fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #22 0x00000030a66aaffc in g_application_run () at /lib64/libgio-2.0.so.0 #23 0x0000003d3d805d60 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #24 0x0000003d3d8057d1 in ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=0x7fff0398f5f0, avalue=0x122cee0) at ../src/x86/ffi64.c:525 #25 0x00007fa6ea8bb464 in pygi_invoke_c_callable () at /usr/lib64/python2.7/site-packages/gi/_gi.so #26 0x00007fa6ea8bcd98 in pygi_function_cache_invoke () at /usr/lib64/python2.7/site-packages/gi/_gi.so #27 0x00007fa6ea8b14be in _callable_info_call () at /usr/lib64/python2.7/site-packages/gi/_gi.so #28 0x0000003d3dc4a8d3 in PyObject_Call (func=<gi.FunctionInfo at remote 0x7fa6e5a7be30>, arg=<optimized out>, kw=<optimized out>) at /usr/src/debug/Python-2.7.8/Objects/abstract.c:2529 #29 0x0000003d3dce0615 in PyEval_EvalFrameEx (nk=<optimized out>, na=<optimized out>, pp_stack=<optimized out>, func=<optimized out>) at /usr/src/debug/Python-2.7.8/Python/ceval.c:4328 #30 0x0000003d3dce0615 in PyEval_EvalFrameEx (oparg=<optimized out>, pp_stack=<optimized out>) at /usr/src/debug/Python-2.7.8/Python/ceval.c:4133
New pygobject3 crashes for me as well. No substantial changes in backtrace.
I found a temporary solution. I downgraded packages to the version 3.12.1-1 bash$ rpm -qa pygobject3* pygobject3-base-3.12.1-1.fc21.x86_64 pygobject3-3.12.1-1.fc21.x86_64
Unfortunately no one really watches the pygobject redhat bug tracker, but the upstream guys are quite responsive. I encourage someone who can reproduce to file a bug in bugzilla.gnome.org (i haven't updated to f21 yet...)
I'm seeing this too
Reported upstream as apparently we don't have an active maintainer in Fedora in the hope we get some form of response that's useful. I also think this needs to be an alpha blocker as it impacts testing F-21 on F-21
virt stuff blocks Beta, not Alpha. Proposing as a Beta blocker per criterion "The release must be able host virtual guest instances of the same release." - not a slam dunk as it works without the UI, but we can discuss it. https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Self_hosting_virtualization
also note that Boxes works, so long as you use permissive SELinux due to the rados2 execstack bug ( https://bugzilla.redhat.com/show_bug.cgi?id=1118504 ).
This just got fixed upstream in https://bugzilla.gnome.org/show_bug.cgi?id=735090 and I've backported the fix to the F21 / rawhide packages.
I just pulled the pygobject3-3.13.90-2.fc21 packages and can verify that the patch does fix the issue. Thanks, Kalev!
Ok for me :), thanks :)