Description of problem: Unlocked screen using fingerprint reader Version-Release number of selected component: gnome-shell-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change executable: /usr/bin/gnome-shell kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 atk_object_notify_state_change at atkobject.c:1188 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:522 #3 gjs_invoke_c_function at gi/function.c:894 #4 function_call at gi/function.c:1203 #5 CallJSNative at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372 #6 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:345 #7 js::mjit::stubs::SlowCall at /usr/src/debug/mozjs17.0.0/js/src/methodjit/InvokeHelpers.cpp:133 #8 js::mjit::ic::NativeCall at /usr/src/debug/mozjs17.0.0/js/src/methodjit/MonoIC.cpp:1010 #9 ?? Potential duplicate: bug 904819
Created attachment 855578 [details] File: backtrace
Created attachment 855579 [details] File: cgroup
Created attachment 855580 [details] File: core_backtrace
Created attachment 855581 [details] File: dso_list
Created attachment 855582 [details] File: environ
Created attachment 855583 [details] File: exploitable
Created attachment 855584 [details] File: limits
Created attachment 855585 [details] File: maps
Created attachment 855586 [details] File: open_fds
Created attachment 855587 [details] File: proc_pid_status
Created attachment 855588 [details] File: var_log_messages
Another user experienced a similar problem: Crash while browsing the web in Firefox, nothing in particular done. reporter: libreport-2.1.12 abrt_installed_version: abrt-2.1.12-1.fc20.x86_64 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change executable: /usr/bin/gnome-shell kernel: 3.12.9-301.fc20.x86_64 libreport_version: libreport-2.1.12-1.fc20.x86_64 package: gnome-shell-3.10.3-4.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 satyr_version: satyr-0.13-1.fc20.x86_64 type: CCpp uid: 1000
Another user experienced a similar problem: Unlocking the screen reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change executable: /usr/bin/gnome-shell kernel: 3.13.2-200.fc20.x86_64 package: gnome-shell-3.10.3-6.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Created attachment 863985 [details] File: backtrace
Another user experienced a similar problem: Unlocking screen reporter: libreport-2.2.0 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change executable: /usr/bin/gnome-shell kernel: 3.13.8-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 opened recent chats from the skype gnome extension (https://extensions.gnome.org/extension/696/skype-integration/). This crashed the gnome-shell with SIGSEGV and the shell was immediately restarted. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change environ: executable: /usr/bin/gnome-shell kernel: 3.16.2-200.fc20.x86_64 package: gnome-shell-3.10.4-8.fc20 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: atk_object_notify_state_change executable: /usr/bin/gnome-shell kernel: 3.17.8-200.fc20.x86_64 package: gnome-shell-3.10.4-9.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.