Description of problem: I had the virt-manager running for a few hours. I simply changed window to the virt-manager, started on of the VMs and the crash occurred. I restarted virt-manager and all was back to normal so I will tryto recreate. 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_callable_info_is_method executable: /usr/bin/python2.7 kernel: 3.11.10-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Dec 10 11:22:10 F19-rooksy abrt-hook-ccpp[30801]: Saved core dump of pid 6967 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-12-10-11:22:07-6967 (313655296 bytes) Truncated backtrace: Thread no. 1 (10 frames) #3 g_callable_info_is_method at girepository/gicallableinfo.c:150 #4 g_callable_info_get_ffi_arg_types at girepository/girffi.c:167 #5 g_callable_info_prepare_closure at girepository/girffi.c:373 #6 _pygi_make_native_closure at pygi-closure.c:637 #7 _pygi_marshal_from_py_interface_callback at pygi-marshal-from-py.c:1473 #8 _invoke_marshal_in_args at pygi-invoke.c:515 #9 pygi_callable_info_invoke at pygi-invoke.c:659 #10 ext_do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4408 #11 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2779 #12 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:3330
Created attachment 834614 [details] File: backtrace
Created attachment 834615 [details] File: cgroup
Created attachment 834616 [details] File: core_backtrace
Created attachment 834617 [details] File: dso_list
Created attachment 834618 [details] File: environ
Created attachment 834619 [details] File: limits
Created attachment 834620 [details] File: maps
Created attachment 834621 [details] File: open_fds
Created attachment 834622 [details] File: proc_pid_status
*** Bug 1051312 has been marked as a duplicate of this bug. ***
*** Bug 1036850 has been marked as a duplicate of this bug. ***
*** Bug 1036709 has been marked as a duplicate of this bug. ***
*** Bug 985128 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.