Version-Release number of selected component: gnome-shell-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 14986 Truncated backtrace: Thread no. 1 (10 frames) #0 js::Shape::finalize at /usr/src/debug/mozjs17.0.0/js/src/jspropertytree.cpp:210 #1 finalize<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:355 #2 FinalizeTypedArenas<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:419 #3 js::gc::FinalizeArenas at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:460 #4 foregroundFinalize at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3803 #5 SweepPhase at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3823 #6 IncrementalCollectSlice at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4245 #7 GCCycle at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4408 #8 Collect at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4516 #9 js_InvokeOperationCallback at /usr/src/debug/mozjs17.0.0/js/src/jscntxt.cpp:1028 Potential duplicate: bug 1034467
Created attachment 887780 [details] File: backtrace
Created attachment 887781 [details] File: cgroup
Created attachment 887782 [details] File: core_backtrace
Created attachment 887783 [details] File: dso_list
Created attachment 887784 [details] File: environ
Created attachment 887785 [details] File: exploitable
Created attachment 887786 [details] File: limits
Created attachment 887787 [details] File: maps
Created attachment 887788 [details] File: open_fds
Created attachment 887789 [details] File: proc_pid_status
Created attachment 887790 [details] File: var_log_messages
Another user experienced a similar problem: I was use a google-chrome in my main screen and I've tried to install skype on terminal in my second screen, and the gnome bar and windows decorations was disappeared reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize 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 SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: 1. Locked the screen. 2. When typed password to unlock, gnome-shell crashed. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize 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 SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Gnome Shell suddenly crashes and then is being restarted. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize 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 SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Connected to VPN (NetworkManager). Once established GnomeShell crashed, restarted and VPN was still active and running. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.14.3-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Happened a few minutes after suspend/resume. That seems to be the only apparent consistent feature. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.14.3-200.fc20.x86_64 package: gnome-shell-3.10.4-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: nothing much happening at all I was actually using a different laptop and this one was idle when this happened. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.14.4-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This crash occured when I woke up my PC by moving the mouse, lighting the screen, and typed my password on the screen lock. Gnome 3 then restarted by itself, after this crash I presume. Here are the apps that were running : Firefox 29.0 and Mumble 1.2.5 reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.14.4-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I just open a web browser. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10fa0cf5237d4b6087139973998667343200000021010000 crash_function: js::Shape::finalize executable: /usr/bin/gnome-shell kernel: 3.15.5-200.fc20.x86_64 package: gnome-shell-3.10.4-5.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This seems to occur fairly reliably when I resuem from suspend. Not always, but frequently, and only occasionally under other circumstances.
It doesn't even need a suspend. Resuming from screensaver does it in. At least it restarts.
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.