Description of problem: Just crashed unexpectedly. 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: unowned executable: /usr/bin/gnome-shell kernel: 3.11.6-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 unowned at /usr/src/debug/mozjs17.0.0/js/src/jsscope.h:373 #1 StackShape at /usr/src/debug/mozjs17.0.0/js/src/jsscope.h:989 #2 js::Shape::removeChild at /usr/src/debug/mozjs17.0.0/js/src/jspropertytree.cpp:119 #3 js::Shape::finalize at /usr/src/debug/mozjs17.0.0/js/src/jspropertytree.cpp:211 #4 finalize<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:355 #5 FinalizeTypedArenas<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:419 #6 js::gc::FinalizeArenas at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:460 #7 foregroundFinalize at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3803 #8 SweepPhase at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3823 #9 IncrementalCollectSlice at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4245
Created attachment 819626 [details] File: backtrace
Created attachment 819627 [details] File: cgroup
Created attachment 819628 [details] File: core_backtrace
Created attachment 819629 [details] File: dso_list
Created attachment 819630 [details] File: environ
Created attachment 819631 [details] File: exploitable
Created attachment 819632 [details] File: limits
Created attachment 819633 [details] File: maps
Created attachment 819634 [details] File: open_fds
Created attachment 819635 [details] File: proc_pid_status
Created attachment 819636 [details] File: var_log_messages
I woke up the computer from suspended mode when the crash took place. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.11.9-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
It happened after coming up from suspension mode. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.11.9-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: unlock screensaver reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned 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 SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: It occured randomly this time reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned 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 SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: It happened while using firefox 26 menu customize reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.12.6-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: keeps crashing. Dont know exact reason. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.12.6-300.fc20.i686 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Resumed the laptop from suspend reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.12.8-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I turned off wireless swith and found air plane mode activated and I turned off air plane mode, that where at least I think gnome-shell crashed. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.12.9-301.fc20.x86_64 package: gnome-shell-3.10.3-3.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Nothing done, really.. it was not under pressure, no user interaction taking place. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.12.10-300.fc20.x86_64 package: gnome-shell-3.10.3-4.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I tried to unlock the screen after being away from the system for about ten hours. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10564bda675ac06b6d139321122396324900000016210000 crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.13.3-201.fc20.x86_64 package: gnome-shell-3.10.4-1.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This was pretty much out of the blue. No idea what could have triggered it. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.13.5-200.fc20.x86_64 package: gnome-shell-3.10.4-1.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Open a child windows, eg from evolution open a compose new message window, or open a movie, or a picture /big picture, about 8-12Mpixel/ reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.13.6-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Clicking between windows. Happens roughly every 6 hours. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.13.6-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
Earlier this week I upgraded Gnome to 3.12 using the instructions here: http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/ So far I have not seen this crash happen, where it had been happening several times a day when running 3.10.
(In reply to rich from comment #25) > Earlier this week I upgraded Gnome to 3.12 using the instructions here: > http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/ > > So far I have not seen this crash happen, where it had been happening > several times a day when running 3.10. I decided to try the same as I've been experience the crash multiple times per day also. So far, after 1 day, so good. I'll post back in a few days with further results. By the way, the only issue I had with doing the upgrade was getting Cairo-Dock working again. I had to compile myself and it's only partially working. But, so far, all other applications are working.
I upgraded too to Gnome 3.12 and so far not a single crash on my desktop nor my laptop.
So I've been on the new Gnome 3.12 for about a week and no crashes. It is running quite well, actually! The only item that was difficult about the migration was getting Cairo-Dock to work again (had to compile it myself).
FWIW I'm more than a week into using the Gnome 3.12 COPR builds, and not a single crash on three systems -- Coming from multiple crashes daily.
Another user experienced a similar problem: Went to copy and paste something from Libreoffice to Gnome terminal and it crashed reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: unowned executable: /usr/bin/gnome-shell kernel: 3.13.9-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
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.