Bug 1116661

Summary: [abrt] gnome-session: gnome-session-failed killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: cschalle, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/36a0fa0ff911961b1090abd706c76ce079550585
Whiteboard: abrt_hash:bfec5d4aa79bbb8c16845a7be21210ba614b171a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:54:10 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Chris Murphy 2014-07-07 01:32:32 UTC 
Version-Release number of selected component:
gnome-session-3.12.1-3.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-session-failed --extensions
executable:     /usr/libexec/gnome-session-failed
kernel:         3.16.0-0.rc3.git2.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 pango_cairo_fc_font_map_fontset_key_substitute at pangocairo-fcfontmap.c:114
 #2 pango_fc_font_map_get_patterns at pangofc-fontmap.c:1674
 #3 pango_fc_font_map_load_fontset at pangofc-fontmap.c:1776
 #4 pk_pango_fc_font_map_load_fontset at /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so
 #5 itemize_state_update_for_new_run at pango-context.c:1412
 #6 itemize_state_process_run at pango-context.c:1451
 #7 pango_itemize_with_base_dir at pango-context.c:1590
 #8 pango_layout_check_lines at pango-layout.c:3998
 #9 pango_layout_get_extents_internal at pango-layout.c:2587
Comment 1 Chris Murphy 2014-07-07 01:32:40 UTC 
Created attachment 915936 [details]
File: backtrace
Comment 2 Chris Murphy 2014-07-07 01:32:43 UTC 
Created attachment 915937 [details]
File: cgroup
Comment 3 Chris Murphy 2014-07-07 01:32:46 UTC 
Created attachment 915938 [details]
File: core_backtrace
Comment 4 Chris Murphy 2014-07-07 01:32:49 UTC 
Created attachment 915939 [details]
File: dso_list
Comment 5 Chris Murphy 2014-07-07 01:32:50 UTC 
Created attachment 915940 [details]
File: environ
Comment 6 Chris Murphy 2014-07-07 01:32:54 UTC 
Created attachment 915941 [details]
File: exploitable
Comment 7 Chris Murphy 2014-07-07 01:32:56 UTC 
Created attachment 915942 [details]
File: limits
Comment 8 Chris Murphy 2014-07-07 01:33:04 UTC 
Created attachment 915943 [details]
File: maps
Comment 9 Chris Murphy 2014-07-07 01:33:07 UTC 
Created attachment 915944 [details]
File: open_fds
Comment 10 Chris Murphy 2014-07-07 01:33:08 UTC 
Created attachment 915945 [details]
File: proc_pid_status
Comment 11 Chris Murphy 2014-07-07 01:33:11 UTC 
Created attachment 915946 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 16:06:34 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:54:10 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.