Description of problem: I tried to run a wireshark within and outside of the virtual guest at the same time. Both must have depleated the available memory, causing this crash. Version-Release number of selected component: virt-manager-0.9.5-1.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: python /usr/share/virt-manager/virt-manager.py crash_function: dequeue_pending_request executable: /usr/bin/python2.7 kernel: 3.9.9-201.fc18.x86_64 runlevel: N 5 uid: 10004 var_log_messages: Jul 22 11:38:14 alp-desk1 abrt[13954]: Saved core dump of pid 21444 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-07-22-11:38:11-21444 (424685568 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #4 dequeue_pending_request at xcb_io.c:177 #6 XGetWindowProperty at GetProp.c:69 #7 fetch_net_wm_check_window at gdkevents-x11.c:2671 #8 gdk_x11_screen_supports_net_wm_hint at gdkevents-x11.c:2852 #9 gdk_x11_window_set_user_time at gdkwindow-x11.c:3741 #10 setup_toplevel_window at gdkwindow-x11.c:637 #11 _gdk_window_impl_new at gdkwindow-x11.c:821 #12 gdk_window_new at gdkwindow.c:1456 #13 gtk_window_realize at gtkwindow.c:4843 #18 gtk_widget_realize at gtkwidget.c:3561
Created attachment 776835 [details] File: backtrace
Created attachment 776836 [details] File: cgroup
Created attachment 776837 [details] File: core_backtrace
Created attachment 776838 [details] File: dso_list
Created attachment 776839 [details] File: environ
Created attachment 776840 [details] File: limits
Created attachment 776841 [details] File: maps
Created attachment 776842 [details] File: open_fds
Created attachment 776843 [details] File: proc_pid_status
Is this reliably reproducible? Are you running on kde by any chance? I've seen similar reports like this from oxygen theme users: https://bugzilla.redhat.com/show_bug.cgi?id=889771
Yes you are right - I am running with KDE on FC17, and the oxygen theme. But I also see strange GTK behaviour when running with the Raleigh theme.
Not sure about that other theme, maybe this is just some generic gtk-on-kde issue. Duping to the similar report. *** This bug has been marked as a duplicate of bug 889771 ***