Version-Release number of selected component: gnome-shell-3.10.2.1-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.11.9-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 js_malloc at dist/include/js/Utility.h:157 #4 malloc_ at /usr/src/debug/mozjs17.0.0/js/src/jsalloc.h:68 #5 createTable at dist/include/js/HashTable.h:314 #6 init at dist/include/js/HashTable.h:369 #8 Snapshot at /usr/src/debug/mozjs17.0.0/js/src/jsiter.cpp:214 #9 js::GetPropertyNames at /usr/src/debug/mozjs17.0.0/js/src/jsiter.cpp:346 #10 obj_getOwnPropertyNames at /usr/src/debug/mozjs17.0.0/js/src/jsobj.cpp:1769 #11 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372 #12 js::Interpret at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:2414 #13 UncachedInlineCall at /usr/src/debug/mozjs17.0.0/js/src/methodjit/InvokeHelpers.cpp:327
Created attachment 829824 [details] File: backtrace
Created attachment 829825 [details] File: cgroup
Created attachment 829826 [details] File: core_backtrace
Created attachment 829827 [details] File: dso_list
Created attachment 829828 [details] File: environ
Created attachment 829829 [details] File: exploitable
Created attachment 829830 [details] File: limits
Created attachment 829831 [details] File: maps
Created attachment 829832 [details] File: open_fds
Created attachment 829833 [details] File: proc_pid_status
Created attachment 829834 [details] File: var_log_messages
Crash happened right after gnome-initial-setup after an install of f20 Final TC3 in French. Didn't happen in English installs. reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: gnome-shell --mode=initial-setup crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.11.9-300.fc20.x86_64 package: gnome-shell-3.10.2.1-2.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 992
Proposing as a Final blocker: this violates https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#SELinux_and_crash_notifications - "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." - when installing in French.
Hum, wasn't able to reproduce on a subsequent try. Might make it harder to debug :/ The other reporter has a French name so I'm sticking by the French connection...
I performed a French install of TC3 Live, but I haven't see any crash after g-i-s.
Discussed at 2013-12-02 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.log.txt . This seems too slippery and unreproducible to make it a blocker. We are open to the possibility of taking a fix for it if someone happens to pin down the problem and it looks like it could occur commonly and be clean to fix, but we didn't want to definitely vote it +1 FE without more solid information; if someone does happen to come across a clean reproducer/fix, please propose it.
Another user experienced a similar problem: I had upgraded the system from FC18 to FC20 through fedup. My home partition is encrypted & is btrfs raid 1 etc so I mount it manually, therefore it was not mounted automatically on reboot after upgrade. but there still is an empty dummy dir structure for /home with users home dirs in it over which I mount my actual home partition after its assemblage. So my /home/vikram directory may be completely empty when I first logged in to the system after upgrade. Thats all there is to for uniqueness of the situation. I normally use KDE & not Gnome & I am not sure if it was KDE or Gnome into which I first logged into after upgrade. It could be both, I think, one by one, i.e.... Thanks! reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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 5 type: CCpp uid: 42
Another user experienced a similar problem: May be related to Bugzilla #812624, noted 100% on one cpu for gnome-shell. Ran systemctl start plymouth-quit.service per Bugzilla #870695, system did not restart gdm login. Used old telinit3/5 trick to restart gdm. Ran /usr/libexec/plymouth/plymouth-update-initrd - again per Bugzilla #870695 - and rebooted after, ABRT report generated upon login. No further problem noted on succesive reboots. HISTORY: Installed system Dec 21 from F20 release DVD, updates done immediately thereafter. No issues noted. Updates done again on Dec 23, reboot after showed gnome-shell 100% problem. NOTE: System booted with Fedora splash screen until fisrt updates run. Grub in console mode, and text-mode boot are now normal, cannot see where to activate spalsh screen boot. Doesn't plymouth provide this? The following updates were installed Dec 23: Dec 23 15:55:22 Updated: nss-sysinit-3.15.3.1-1.fc20.x86_64 Dec 23 15:55:31 Updated: nss-3.15.3.1-1.fc20.x86_64 Dec 23 15:55:31 Updated: boost-system-1.54.0-9.fc20.x86_64 Dec 23 15:55:32 Updated: 1:dbus-libs-1.6.12-7.fc20.x86_64 Dec 23 15:55:35 Updated: 1:dbus-1.6.12-7.fc20.x86_64 Dec 23 15:55:36 Updated: PackageKit-glib-0.8.15-1.fc20.x86_64 Dec 23 15:55:36 Updated: PackageKit-yum-0.8.15-1.fc20.x86_64 Dec 23 15:55:39 Updated: PackageKit-0.8.15-1.fc20.x86_64 Dec 23 15:55:42 Updated: ca-certificates-2013.1.95-1.fc20.noarch Dec 23 15:55:44 Updated: 1:openssl-libs-1.0.1e-36.fc20.x86_64 Dec 23 15:55:44 Updated: 1:NetworkManager-glib-0.9.9.0-22.git20131003.fc20.x86_64 Dec 23 15:55:45 Updated: boost-chrono-1.54.0-9.fc20.x86_64 Dec 23 15:55:46 Updated: boost-thread-1.54.0-9.fc20.x86_64 Dec 23 15:55:47 Updated: nss-tools-3.15.3.1-1.fc20.x86_64 Dec 23 15:55:48 Updated: libreswan-3.7-1.fc20.x86_64 Dec 23 15:55:49 Updated: boost-locale-1.54.0-9.fc20.x86_64 Dec 23 15:55:51 Updated: 1:NetworkManager-0.9.9.0-22.git20131003.fc20.x86_64 Dec 23 15:55:52 Updated: 1:openssl-1.0.1e-36.fc20.x86_64 Dec 23 15:55:55 Updated: rubygems-2.1.11-114.fc20.noarch Dec 23 15:55:55 Updated: PackageKit-yum-plugin-0.8.15-1.fc20.x86_64 Dec 23 15:55:56 Updated: PackageKit-command-not-found-0.8.15-1.fc20.x86_64 Dec 23 15:55:56 Updated: PackageKit-gtk3-module-0.8.15-1.fc20.x86_64 Dec 23 15:55:57 Updated: PackageKit-gstreamer-plugin-0.8.15-1.fc20.x86_64 Dec 23 15:55:57 Updated: 1:dbus-x11-1.6.12-7.fc20.x86_64 Dec 23 15:55:58 Updated: boost-filesystem-1.54.0-9.fc20.x86_64 Dec 23 15:55:59 Updated: boost-python-1.54.0-9.fc20.x86_64 Dec 23 15:56:06 Updated: 2:gedit-3.10.3-1.fc20.x86_64 Dec 23 15:56:10 Updated: 1:valgrind-3.9.0-5.fc20.x86_64 Dec 23 15:56:11 Updated: boost-iostreams-1.54.0-9.fc20.x86_64 Dec 23 15:56:12 Updated: boost-date-time-1.54.0-9.fc20.x86_64 Dec 23 15:56:16 Updated: 1:eclipse-pydev-3.1.0-1.fc20.noarch Dec 23 15:56:17 Updated: libburn-1.3.4-1.fc20.x86_64 Dec 23 15:56:18 Updated: icedtea-web-1.4.1-1.fc20.x86_64 Dec 23 15:56:20 Updated: shotwell-0.15.1-1.fc20.x86_64 Dec 23 15:56:21 Updated: libisofs-1.3.4-1.fc20.x86_64 Dec 23 15:56:23 Updated: tzdata-java-2013i-1.fc20.noarch Dec 23 15:56:23 Updated: boost-signals-1.54.0-9.fc20.x86_64 Dec 23 15:56:24 Updated: autoconf-2.69-14.fc20.noarch Dec 23 15:56:29 Updated: tzdata-2013i-1.fc20.noarch Dec 23 15:56:31 Updated: gnupg-1.4.16-2.fc20.x86_64 Dec 23 15:56:32 Updated: boost-regex-1.54.0-9.fc20.x86_64 Dec 23 15:56:33 Updated: boost-program-options-1.54.0-9.fc20.x86_64 reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 42
Another user experienced a similar problem: found the crash on login reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 42
Another user experienced a similar problem: I logged out. When logging in again I got a remainder from ABRT that gnome-shell crashed. I did not see or do anything special. No loss of functionality while using Gnome. reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.12.8-300.fc20.x86_64 package: gnome-shell-3.10.3-1.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Logged in using GNOME Classic session reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.13.3-201.fc20.x86_64 package: gnome-shell-3.10.3-7.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: gnome-shell hangs after installing multiple fonts with gnome-font-viewer reporter: libreport-2.2.0 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 42
Another user experienced a similar problem: I started Cinamon which didn't show the desktop so HUPPED the cinnamon-session & started again but now manually selected Cinnamon. It behaved sluggish so I checked - top - which showed 2 gnome-shell processes under user gdm consuming aroung 85 cinnamon-session% - 95% CPU. I brought the system to init 3 but the shell process didn't die. The I HUPPED the lower PID process which exited it but had to kill the higher PID process with signal 9 from root console. Killed all user processes with pkill -u <user> Renetered init 5 but didn't login yet & again one g-shell process under gdm started consuming which I kelled with -9. I logged in with Cinnamon & had to kill another g-shell consuming lots of CPU & making everything slow under user gdm. Thanks reporter: libreport-2.2.1 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 3 5 type: CCpp uid: 42
Another user experienced a similar problem: I don't know reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js_malloc 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
Created attachment 891248 [details] File: backtrace
Another user experienced a similar problem: I had rebooted the system into KDE through GDM. Immedaitely on login to KDE I got this crash. reporter: libreport-2.2.2 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.14.2-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: I had deleted .kde dir & rebooted. reporter: libreport-2.2.2 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.14.2-200.fc20.x86_64 package: gnome-shell-3.10.4-2.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Logged out from KDE. As root killed all processes of the last KDE user by pkill -u vikram & relogged into KDE. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 42
Another user experienced a similar problem: I had rebooted the system & logged into KDE when I found it. reporter: libreport-2.2.2 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc 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: 42
Another user experienced a similar problem: I guess I change the number of attached screens. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js_malloc 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: System was rebooted back into LXDE. This crash happaened at login or somewhere around that. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.16.3-200.fc20.x86_64 package: gnome-shell-3.10.4-8.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Had updated the follwing packages. Don't have any idea if theis crash has any relevance with the updates. Oct 29 13:50:28 Updated: libkworkspace-4.11.13-2.fc20.x86_64 Oct 29 13:50:32 Updated: ksysguard-libs-4.11.13-2.fc20.x86_64 Oct 29 13:50:49 Updated: selinux-policy-3.12.1-192.fc20.noarch Oct 29 13:50:51 Updated: kgreeter-plugins-4.11.13-2.fc20.x86_64 Oct 29 13:50:52 Updated: kde-style-oxygen-4.11.13-2.fc20.x86_64 Oct 29 13:50:53 Updated: kde-workspace-libs-4.11.13-2.fc20.x86_64 Oct 29 13:50:54 Updated: kwin-gles-libs-4.11.13-2.fc20.x86_64 Oct 29 13:50:55 Updated: kdm-4.11.13-2.fc20.x86_64 Oct 29 13:50:56 Updated: kcm_colors-4.11.13-2.fc20.x86_64 Oct 29 13:51:13 Updated: kde-workspace-4.11.13-2.fc20.x86_64 Oct 29 13:51:26 Installed: kernel-3.16.6-203.fc20.x86_64 Oct 29 13:51:27 Updated: ksysguardd-4.11.13-2.fc20.x86_64 Oct 29 13:51:28 Updated: ksysguard-4.11.13-2.fc20.x86_64 Oct 29 13:51:30 Installed: kernel-modules-extra-3.16.6-203.fc20.x86_64 Oct 29 13:51:30 Updated: plasma-scriptengine-python-4.11.13-2.fc20.x86_64 Oct 29 13:51:31 Updated: kde-workspace-ksplash-themes-4.11.13-2.fc20.noarch Oct 29 13:51:32 Updated: kdm-themes-4.11.13-2.fc20.noarch Oct 29 13:51:34 Updated: kde-workspace-devel-4.11.13-2.fc20.x86_64 Oct 29 13:51:55 Updated: selinux-policy-devel-3.12.1-192.fc20.noarch Oct 29 13:52:08 Updated: selinux-policy-doc-3.12.1-192.fc20.noarch Oct 29 13:52:31 Updated: selinux-policy-targeted-3.12.1-192.fc20.noarch Oct 29 13:52:35 Updated: oxygen-cursor-themes-4.11.13-2.fc20.noarch Oct 29 13:53:03 Updated: kde-workspace-debuginfo-4.11.13-2.fc20.x86_64 Oct 29 13:53:05 Updated: gnupg-1.4.18-4.fc20.x86_64 Oct 29 13:53:06 Updated: oxygen-gtk2-1.4.6-1.fc20.x86_64 Oct 29 13:53:41 Installed: kernel-devel-3.16.6-203.fc20.x86_64 Oct 29 13:53:43 Updated: kdeclassic-cursor-theme-4.11.13-2.fc20.noarch Oct 29 13:53:44 Updated: 1:perl-Socket-2.016-1.fc20.x86_64 Oct 29 13:53:46 Updated: kernel-headers-3.16.6-203.fc20.x86_64 Oct 29 13:53:47 Updated: libtdb-1.3.0-2.fc20.x86_64 Oct 29 13:53:52 Updated: mate-themes-1.9.1-1.fc20.noarch then rebooted after some time & logged back into LXDE when I found this crash. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.16.6-203.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Had rebooted into LXDE desktop & found this crash reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: gnome-shell --mode=gdm crash_function: js_malloc executable: /usr/bin/gnome-shell kernel: 3.16.6-203.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
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.