Description of problem: Tried to reload Gnome Shell (replace) by hitting Alt+F2 then 'r'. Gnome Shell was reloaded and suddenly relaunched a second time by itself. Version-Release number of selected component: gnome-shell-3.10.1-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 gray_find_cell at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:533 #7 gray_record_cell at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:553 #8 gray_set_cell at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:596 #9 gray_render_line at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:859 #10 gray_render_cubic at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:1156 #11 gray_cubic_to at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:1213 #12 FT_Outline_Decompose at /usr/src/debug/freetype-2.5.0/src/base/ftoutln.c:253 #13 gray_convert_glyph_inner at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:1783 #14 gray_convert_glyph at /usr/src/debug/freetype-2.5.0/src/smooth/ftgrays.c:1885 #15 ft_smooth_render_generic at /usr/src/debug/freetype-2.5.0/src/smooth/ftsmooth.c:315 Potential duplicate: bug 834726
Created attachment 823344 [details] File: backtrace
Created attachment 823345 [details] File: cgroup
Created attachment 823346 [details] File: core_backtrace
Created attachment 823347 [details] File: dso_list
Created attachment 823348 [details] File: environ
Created attachment 823349 [details] File: limits
Created attachment 823350 [details] File: maps
Created attachment 823351 [details] File: open_fds
Created attachment 823352 [details] File: proc_pid_status
Created attachment 823353 [details] File: var_log_messages
I just press CMD (WIN) key. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10d2b9a650879be0b8138030752083770300000012750000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.11.8-300.fc20.x86_64 package: gnome-shell-3.10.2-1.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
Tried gnome-session --session gnome-wayland and some apps within it. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-shell-wayland --wayland crash_function: gray_find_cell executable: /usr/bin/gnome-shell-wayland kernel: 3.11.8-300.fc20.x86_64 package: gnome-shell-3.10.2-2.fc20 reason: Process /usr/bin/gnome-shell-wayland was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I happened at the first gnome-shell - and X session - start after a full upgrade from fedora 19 to 20 via yum. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.11.10-301.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 3 type: CCpp uid: 1000
Another user experienced a similar problem: I just logged in, actived the Overview and started typing 'steam'... reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10bee322ca4b4e12c7138771006125396300000008040000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.12.5-302.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Created attachment 873770 [details] Crash logs for review if they can help.
Another user experienced a similar problem: I wanted to run an application through overview mode. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10bee322ca4b4e12c7138771006125396300000008040000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.13.5-202.fc20.x86_64 package: gnome-shell-3.10.4-1.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: As usual, I tried to type in the overview, too fast or someting reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 1075c25a04c2ef8df4137787943798685900000014510000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.13.7-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: GNOME Shell sometimes freezes, and after a minute or so crashes and restarts itself. Application windows stay open, but without titlebars, then the titlebars re-appear and you can then keep working where you left off. It's like you did a " Alt+F2 -> r ". reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.13.10-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: ABRT showed up on a reboot after "yum update". I don't know at which point this happened, but I think that I had just logged in (normal F20 Gnome desktop) and was starting up my normal applications (term, firefox, and xchat). reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.15.10-201.fc20.x86_64 package: gnome-shell-3.10.4-8.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1104
Another user experienced a similar problem: Only unlook the screen. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.16.2-201.fc20.x86_64 package: gnome-shell-3.10.4-8.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: As usual, starting overview and typing. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10be3429a4123a0663140806094875951200000017530000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.16.6-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: crashed just after login reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.16.6-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I connected an android (4.4.2) tablet (cheap generic device) to my system via USB 3.0. I then transfured a LibreOffice document from the android device to my system. As I did that I noticed my desktop was spazzing out (Activities button had no text at all and docky had crashed, however the time/date display and options/shutdown button was unaffected), as I proceeded to eject the android device I also noticed the text on the eject conformation window also had text errors (most of the text was missing and the remainder was mis-aligned), the eject operation was successful however. I then did a system reboot via terminal. Once the system was back up, I went on to the software app/interface and attempted to install QElectroTech at which point "Software" crashed and I recived 2 bug report notifications, 1 for "Software" and this one. Further note: I updated daily, this has not happened to me before as far as I'm aware so perhaps the problem stems from one of those updates (15/11/2014 - dd/mm/yyyy). reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.16.7-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Sorry ignored the above comment, the bug discription (comment) and the actual bug are not the related.
Another user experienced a similar problem: Same old, same old. Running Activities and typing. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10ff0744dec902720c141423503837036800000030050000 crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.17.2-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: unlock an locked screen. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gray_find_cell executable: /usr/bin/gnome-shell kernel: 3.17.4-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.