Version-Release number of selected component: gnome-shell-3.10.2.1-3.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: object_instance_trace executable: /usr/bin/gnome-shell kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 object_instance_trace at gi/object.c:1301 #1 processMarkStackTop at /usr/src/debug/mozjs17.0.0/js/src/gc/Marking.cpp:1214 #2 js::GCMarker::drainMarkStack at /usr/src/debug/mozjs17.0.0/js/src/gc/Marking.cpp:1258 #3 DrainMarkStack at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4142 #4 IncrementalCollectSlice at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4203 #5 GCCycle at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4408 #6 Collect at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4516 #7 js_InvokeOperationCallback at /usr/src/debug/mozjs17.0.0/js/src/jscntxt.cpp:1028 #8 js_HandleExecutionInterrupt at /usr/src/debug/mozjs17.0.0/js/src/jscntxt.cpp:1044 #9 js::mjit::stubs::Interrupt at /usr/src/debug/mozjs17.0.0/js/src/methodjit/StubCalls.cpp:764
Created attachment 851204 [details] File: backtrace
Created attachment 851205 [details] File: cgroup
Created attachment 851206 [details] File: core_backtrace
Created attachment 851207 [details] File: dso_list
Created attachment 851208 [details] File: environ
Created attachment 851209 [details] File: exploitable
Created attachment 851210 [details] File: limits
Created attachment 851211 [details] File: maps
Created attachment 851212 [details] File: open_fds
Created attachment 851213 [details] File: proc_pid_status
Created attachment 851214 [details] File: var_log_messages
Another user experienced a similar problem: I am unsure of what occurred. I may have tugged on the VGA cable connected to my laptop accidentally, but the cable never fully disengaged. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: object_instance_trace executable: /usr/bin/gnome-shell kernel: 3.13.3-201.fc20.x86_64 package: gnome-shell-3.10.3-8.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I inserted a thumb drive into the computer. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10f2691028762dfc84139594411643654800000034780000 crash_function: object_instance_trace 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
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.