Version-Release number of selected component: virt-manager-0.10.0-4.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/virt-manager/virt-manager crash_function: _g_log_abort executable: /usr/bin/python2.7 kernel: 3.11.9-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 500 var_log_messages: Dec 2 13:51:49 localhost abrt-hook-ccpp[27115]: Saved core dump of pid 25841 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-12-02-13:51:42-25841 (175972352 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #4 g_callable_info_is_method at girepository/gicallableinfo.c:150 #5 g_callable_info_get_ffi_arg_types at girepository/girffi.c:167 #6 g_callable_info_prepare_closure at girepository/girffi.c:373 #7 _pygi_make_native_closure at pygi-closure.c:637 #8 _pygi_marshal_from_py_interface_callback at pygi-marshal-from-py.c:1473 #9 _invoke_marshal_in_args at pygi-invoke.c:515 #10 pygi_callable_info_invoke at pygi-invoke.c:659 #11 ext_do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4408 #12 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2779
Created attachment 831579 [details] File: backtrace
Created attachment 831580 [details] File: cgroup
Created attachment 831581 [details] File: core_backtrace
Created attachment 831582 [details] File: dso_list
Created attachment 831583 [details] File: environ
Created attachment 831584 [details] File: limits
Created attachment 831585 [details] File: maps
Created attachment 831586 [details] File: open_fds
Created attachment 831587 [details] File: proc_pid_status
Do note that I'm running glib2-2.38.2-1 from F20 on F19
(In reply to David Juran from comment #10) > Do note that I'm running glib2-2.38.2-1 from F20 on F19 Why? Maybe try pulling in f20 pygobject3 as well, could be something that's already fixed there. How reproducible is this?
Why I'm running glib2 from F20? I needed to update evolution (long story) and it required newer glib2 due to silent ABI change, there are was some symbol in F20 glib2 that wasn't in F19. Regarding reproducibility, this crash has only happened one single time so feel free to close the bug, hopefully it's caused by the non-standard package-mix.
(In reply to David Juran from comment #12) > it required newer glib2 due to silent ABI change, there are was some > symbol in F20 glib2 that wasn't in F19. Er...it's totally expected that newer GLib versions have more symbols, but if you're claiming there was a *break*, please provide more information.
*** This bug has been marked as a duplicate of bug 1039786 ***