Version-Release number of selected component: gnome-shell-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gjs_value_from_g_argument executable: /usr/bin/gnome-shell global_pid: 3030 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gjs_value_from_g_argument at gi/arg.cpp:2648 #1 gjs_invoke_c_function at gi/function.cpp:1058 #2 function_call at gi/function.cpp:1319 #3 CallJSNative at /usr/src/debug/mozjs-24.2.0/js/src/jscntxtinlines.h:321 #4 js::Invoke at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:474 #5 Interpret at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:2298 #6 js::RunScript at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:438 #7 js::Invoke at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:500 #8 js::CallOrConstructBoundFunction at /usr/src/debug/mozjs-24.2.0/js/src/jsfun.cpp:1212 #9 CallJSNative at /usr/src/debug/mozjs-24.2.0/js/src/jscntxtinlines.h:321
Created attachment 1012324 [details] File: backtrace
Created attachment 1012325 [details] File: cgroup
Created attachment 1012326 [details] File: core_backtrace
Created attachment 1012327 [details] File: dso_list
Created attachment 1012328 [details] File: environ
Created attachment 1012329 [details] File: limits
Created attachment 1012330 [details] File: maps
Created attachment 1012331 [details] File: mountinfo
Created attachment 1012332 [details] File: namespaces
Created attachment 1012333 [details] File: open_fds
Created attachment 1012334 [details] File: proc_pid_status
Created attachment 1012335 [details] File: var_log_messages
*** Bug 1236275 has been marked as a duplicate of this bug. ***
Still occurring with F23. Both bugs show a crash *during* garbage collection, which is probably a clue about what is wrong.
Another user experienced a similar problem: I honestly have no idea. I just started navigating menus and BAM! reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gjs_value_from_g_argument executable: /usr/bin/gnome-shell global_pid: 2766 kernel: 4.2.3-300.fc23.x86_64 package: gnome-shell-3.18.0-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: 3 5 type: CCpp uid: 1000
Another user experienced a similar problem: I'm really not sure what happened. I closed a couple of notifications and suddenly I was informed Gnome shell had quit reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gjs_value_from_g_argument executable: /usr/bin/gnome-shell global_pid: 3445 kernel: 4.2.6-301.fc23.x86_64 package: gnome-shell-3.18.3-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1002
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.