Description of problem: Tried to take screenshot (Alt+prtscr) Version-Release number of selected component: gnome-screenshot-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: gnome-screenshot --window crash_function: screenshot_fallback_get_pixbuf executable: /usr/bin/gnome-screenshot global_pid: 24590 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Thu 2015-05-14 12:59:36 BST, end at Thu 2015-06-04 15:33:00 BST. -- Truncated backtrace: Thread no. 1 (6 frames) #0 screenshot_fallback_get_pixbuf at screenshot-utils.c:508 #1 screenshot_get_pixbuf at screenshot-utils.c:660 #2 finish_prepare_screenshot at screenshot-application.c:497 #3 prepare_screenshot_timeout at screenshot-application.c:595 #7 g_main_context_iteration at gmain.c:3869 #8 g_application_run at gapplication.c:2308 Potential duplicate: bug 1118815
Created attachment 1034754 [details] File: backtrace
Created attachment 1034755 [details] File: cgroup
Created attachment 1034756 [details] File: core_backtrace
Created attachment 1034757 [details] File: dso_list
Created attachment 1034758 [details] File: environ
Created attachment 1034759 [details] File: limits
Created attachment 1034760 [details] File: maps
Created attachment 1034761 [details] File: mountinfo
Created attachment 1034762 [details] File: namespaces
Created attachment 1034763 [details] File: open_fds
Created attachment 1034764 [details] File: proc_pid_status
*** Bug 1118815 has been marked as a duplicate of this bug. ***
I've uninstalled abrt, so I cant confirm the message, but pressing Print has no effect in F22. I double-checked keyboard shortcuts.
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.