Description of problem: I clicked on shutdown button in VM it was frozen for a few seconds and crashed after that. How reproducible: Sporadically Actual result: Crash Excepted result: Shutdown a VM Version-Release number of selected component: virt-manager-1.2.1-2.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager crash_function: gtk_widget_update_pango_context executable: /usr/bin/python2.7 global_pid: 3957 kernel: 4.1.7-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 gtk_widget_update_pango_context at gtkwidget.c:10316 #1 g_cclosure_marshal_VOID__FLAGSv at gmarshal.c:1570 #2 _g_closure_invoke_va at gclosure.c:831 #5 gtk_widget_propagate_state at gtkwidget.c:12765 #6 gtk_widget_update_state_flags at gtkwidget.c:8775 #7 gtk_widget_unset_state_flags at gtkwidget.c:8844 #8 gtk_real_menu_item_deselect at gtkmenuitem.c:1769
Created attachment 1082277 [details] File: backtrace
Created attachment 1082278 [details] File: cgroup
Created attachment 1082279 [details] File: core_backtrace
Created attachment 1082280 [details] File: dso_list
Created attachment 1082281 [details] File: environ
Created attachment 1082282 [details] File: limits
Created attachment 1082283 [details] File: maps
Created attachment 1082284 [details] File: mountinfo
Created attachment 1082285 [details] File: namespaces
Created attachment 1082286 [details] File: open_fds
Created attachment 1082287 [details] File: proc_pid_status
Created attachment 1082288 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.