Description of problem: virt-manager had been running for some time with a guest opened in full-screen mode on one of my two monitors; I got this abrt report when it crashed. I'm not sure what I did in particular to trigger the crash. Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: spice_logv executable: /usr/bin/python2.7 kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 14986 var_log_messages: Jan 27 06:55:06 office abrt[18247]: Saved core dump of pid 28243 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2013-01-27-06:54:56-28243 (573181952 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 spice_logv at log.c:109 #3 spice_log at log.c:123 #4 canvas_get_image_internal at ../spice-common/common/canvas_base.c:1132 #5 canvas_get_image at ../spice-common/common/canvas_base.c:1268 #6 canvas_draw_copy at ../spice-common/common/canvas_base.c:2198 #7 display_handle_draw_copy at channel-display.c:1379 #8 spice_channel_recv_msg at spice-channel.c:1860 #9 spice_channel_iterate at spice-channel.c:2073 #10 spice_channel_coroutine at spice-channel.c:2304 #11 coroutine_trampoline at coroutine_ucontext.c:56
Created attachment 688437 [details] File: backtrace
Created attachment 688438 [details] File: build_ids
Created attachment 688439 [details] File: cgroup
Created attachment 688440 [details] File: core_backtrace
Created attachment 688441 [details] File: dso_list
Created attachment 688442 [details] File: environ
Created attachment 688443 [details] File: limits
Created attachment 688444 [details] File: maps
Created attachment 688445 [details] File: open_fds
Created attachment 688446 [details] File: proc_pid_status
Created attachment 688447 [details] File: smolt_data
Same at my system. I have open an application inside an virtual Windows system from virt-manager.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.