Bug 1228288

Summary: [abrt] gnome-screenshot: screenshot_fallback_get_pixbuf(): gnome-screenshot killed by SIGSEGV
Product: [Fedora] Fedora Reporter: leigh scott <leigh123linux>
Component: gnome-screenshotAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ccecchi, leigh123linux, marius.andreiana, mark, mclasen, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cd865510656a23700d6bf7380971aa2769d78dcb
Whiteboard: abrt_hash:3c30f906af85d0f049ea0cb6556f78acdda76aa7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:37:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description leigh scott 2015-06-04 14:36:34 UTC
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

Comment 1 leigh scott 2015-06-04 14:36:37 UTC
Created attachment 1034754 [details]
File: backtrace

Comment 2 leigh scott 2015-06-04 14:36:38 UTC
Created attachment 1034755 [details]
File: cgroup

Comment 3 leigh scott 2015-06-04 14:36:39 UTC
Created attachment 1034756 [details]
File: core_backtrace

Comment 4 leigh scott 2015-06-04 14:36:41 UTC
Created attachment 1034757 [details]
File: dso_list

Comment 5 leigh scott 2015-06-04 14:36:42 UTC
Created attachment 1034758 [details]
File: environ

Comment 6 leigh scott 2015-06-04 14:36:43 UTC
Created attachment 1034759 [details]
File: limits

Comment 7 leigh scott 2015-06-04 14:36:44 UTC
Created attachment 1034760 [details]
File: maps

Comment 8 leigh scott 2015-06-04 14:36:45 UTC
Created attachment 1034761 [details]
File: mountinfo

Comment 9 leigh scott 2015-06-04 14:36:46 UTC
Created attachment 1034762 [details]
File: namespaces

Comment 10 leigh scott 2015-06-04 14:36:47 UTC
Created attachment 1034763 [details]
File: open_fds

Comment 11 leigh scott 2015-06-04 14:36:49 UTC
Created attachment 1034764 [details]
File: proc_pid_status

Comment 12 leigh scott 2015-06-04 14:38:23 UTC
*** Bug 1118815 has been marked as a duplicate of this bug. ***

Comment 13 Marius Andreiana 2015-07-13 21:31:47 UTC
I've uninstalled abrt, so I cant confirm the message, but pressing Print has no effect in F22. I double-checked keyboard shortcuts.

Comment 14 Fedora End Of Life 2016-07-19 14:37:41 UTC
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.