Description of problem: This error just happens. It usually happens when going into application overview or when clicking the user menu. Version-Release number of selected component: gnome-shell-3.8.1-1.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.9.0-0.rc7.git3.1.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #6 gray_find_cell at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:491 #7 gray_record_cell at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:511 #8 gray_set_cell at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:554 #9 gray_render_line at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:845 #10 gray_line_to at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:1147 #11 FT_Outline_Decompose at /usr/src/debug/freetype-2.4.11/src/base/ftoutln.c:160 #12 gray_convert_glyph_inner at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:1736 #13 gray_convert_glyph at /usr/src/debug/freetype-2.4.11/src/smooth/ftgrays.c:1838 #14 ft_smooth_render_generic at /usr/src/debug/freetype-2.4.11/src/smooth/ftsmooth.c:316 #15 FT_Render_Glyph_Internal at /usr/src/debug/freetype-2.4.11/src/base/ftobjs.c:4027 Potential duplicate: bug 834726
Created attachment 739478 [details] File: backtrace
Created attachment 739479 [details] File: cgroup
Created attachment 739480 [details] File: core_backtrace
Created attachment 739481 [details] File: dso_list
Created attachment 739482 [details] File: environ
Created attachment 739483 [details] File: limits
Created attachment 739484 [details] File: maps
Created attachment 739485 [details] File: open_fds
Created attachment 739486 [details] File: proc_pid_status
Created attachment 739487 [details] File: var_log_messages
Created attachment 739488 [details] File: xsession_errors
Just starting the classic session. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --mode=classic crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.10.3-300.fc19.i686 package: gnome-shell-3.8.3-3.fc19 reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors:
I'm getting the same crash in Fedora 20 (with all updates). The function name in the backtrace is slightly different (in mine: "abort", in Charles': __GI_abort). But the real problem is that grey_set_cell seems to invoke a longjmp that fortify thinks is busted. I looked into my backtrace even though abrt said this is the same bug because abrt gets confused by calls to abort. See <https://bugzilla.redhat.com/show_bug.cgi?id=1021328>
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.