Version-Release number of selected component: mate-utils-1.4.0-6.fc18 Additional info: backtrace_rating: 4 cmdline: mate-screenshot --interactive crash_function: handle_error executable: /usr/bin/mate-screenshot kernel: 3.7.5-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #4 handle_error at xcb_io.c:212 #6 XQueryTree at QuTree.c:46 #7 find_wm_window at screenshot-utils.c:530 #8 screenshot_get_pixbuf at screenshot-utils.c:687 #9 check_file_done at mate-screenshot.c:824 #10 mainloop_proxy_func at gioscheduler.c:275 #15 gtk_main at gtkmain.c:1257
Created attachment 694814 [details] File: backtrace
Created attachment 694815 [details] File: cgroup
Created attachment 694816 [details] File: core_backtrace
Created attachment 694817 [details] File: dso_list
Created attachment 694818 [details] File: environ
Created attachment 694819 [details] File: limits
Created attachment 694820 [details] File: maps
Created attachment 694821 [details] File: open_fds
Created attachment 694822 [details] File: proc_pid_status
Created attachment 694823 [details] File: var_log_messages
mate-utils-1.5.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-utils-1.5.0-1.fc18
mate-utils-1.5.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mate-utils-1.5.0-1.fc17
Package mate-utils-1.5.0-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-utils-1.5.0-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2787/mate-utils-1.5.0-1.fc17 then log in and leave karma (feedback).
mate-utils-1.5.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mate-utils-1.5.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.