Version-Release number of selected component: gnome-shell-3.11.5-3.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: FcFontSetMatchInternal executable: /usr/bin/gnome-shell kernel: 3.14.0-0.rc2.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 FcFontSetMatchInternal at fcmatch.c:618 #1 IA__FcFontMatch at fcmatch.c:713 #2 pango_fc_patterns_get_font_pattern at pangofc-fontmap.c:784 #3 pango_fc_fontset_load_next_font at pangofc-fontmap.c:879 #4 pango_fc_fontset_get_font_at at pangofc-fontmap.c:916 #5 pango_fc_fontset_foreach at pangofc-fontmap.c:1038 #6 get_shaper_and_font at pango-context.c:1283 #7 itemize_state_process_run at pango-context.c:1485 #8 pango_itemize_with_base_dir at pango-context.c:1590 #9 pango_layout_check_lines at pango-layout.c:3998
Created attachment 863715 [details] File: backtrace
Created attachment 863716 [details] File: cgroup
Created attachment 863717 [details] File: core_backtrace
Created attachment 863718 [details] File: dso_list
Created attachment 863719 [details] File: environ
Created attachment 863720 [details] File: exploitable
Created attachment 863721 [details] File: limits
Created attachment 863722 [details] File: maps
Created attachment 863723 [details] File: open_fds
Created attachment 863724 [details] File: proc_pid_status
Created attachment 863725 [details] File: var_log_messages
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
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.