Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: - Resumed from hibernation. - On lock screen, un-paused Rhythmbox (streaming radio). - Unlocked screen (using fingerprint reader). - Desktop appeared. - Shell creashed. Version-Release number of selected component: gnome-shell-3.10.2.1-3.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_a 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 g_type_check_instance_is_a at gtype.c:3975 #1 atk_object_notify_state_change at atkobject.c:1188 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:522 #4 gjs_invoke_c_function at gi/function.c:894 #5 function_call at gi/function.c:1203 #6 CallJSNative at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372 #7 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:345 #8 js::Interpret at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:2414 #9 UncachedInlineCall at /usr/src/debug/mozjs17.0.0/js/src/methodjit/InvokeHelpers.cpp:327 Potential duplicate: bug 913358
Created attachment 849753 [details] File: backtrace
Created attachment 849754 [details] File: cgroup
Created attachment 849755 [details] File: core_backtrace
Created attachment 849756 [details] File: dso_list
Created attachment 849757 [details] File: environ
Created attachment 849758 [details] File: exploitable
Created attachment 849759 [details] File: limits
Created attachment 849760 [details] File: maps
Created attachment 849761 [details] File: open_fds
Created attachment 849762 [details] File: proc_pid_status
Created attachment 849763 [details] File: var_log_messages
Another user experienced a similar problem: Playing League of Legends on Wine, spontaneous crash reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_a 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: The gnome shell has crashed after waking up from Sleep state invoked by almost discharged battery on the laptop. NO exact steps to reproduced observed how to easily and repeatedly reproduce. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_a executable: /usr/bin/gnome-shell kernel: 3.11.10-301.fc20.x86_64 package: gnome-shell-3.10.3-4.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Created attachment 865042 [details] File: backtrace
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.