Version-Release number of selected component: gnome-shell-3.30.1-1.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gtk_action_observer_action_removed executable: /usr/bin/gnome-shell journald_cursor: s=17ac6c22e6e24ab2bf151c43b84aca6c;i=5563;b=70974045db9c4484b56b8bf0e95b1db4;m=4f2148bc84;t=578f9302cf42b;x=76cde44583ec9722 kernel: 4.18.14-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_action_observer_action_removed at ../src/gtkactionobserver.c:155 #1 gtk_action_muxer_action_removed at ../src/gtkactionmuxer.c:313 #2 gtk_action_muxer_action_removed_from_group at ../src/gtkactionmuxer.c:326 #3 gtk_action_muxer_remove at ../src/gtkactionmuxer.c:763 #4 gtk_action_muxer_insert at ../src/gtkactionmuxer.c:712 #5 shell_app_update_window_actions at ../src/shell-app.c:472 #6 update_focus_app at ../src/shell-window-tracker.c:487 #12 g_object_notify_by_spec_internal at gobject.c:1181 #13 g_object_notify_by_pspec at gobject.c:1291 #14 ffi_call_unix64 at ../src/x86/unix64.S:76 Potential duplicate: bug 1615135
Created attachment 1497032 [details] File: backtrace
Created attachment 1497033 [details] File: cgroup
Created attachment 1497034 [details] File: core_backtrace
Created attachment 1497035 [details] File: cpuinfo
Created attachment 1497036 [details] File: dso_list
Created attachment 1497037 [details] File: environ
Created attachment 1497038 [details] File: exploitable
Created attachment 1497039 [details] File: limits
Created attachment 1497040 [details] File: maps
Created attachment 1497041 [details] File: mountinfo
Created attachment 1497042 [details] File: open_fds
Created attachment 1497043 [details] File: proc_pid_status
Created attachment 1497044 [details] File: var_log_messages
*** Bug 1649608 has been marked as a duplicate of this bug. ***
*** Bug 1683143 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Clicking on Geary's application menu crashed the shell. How reproducible: random, happened only once so far Steps to reproduce: 1. Click on Geary's application menu to open it. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gtk_action_observer_action_removed executable: /usr/bin/gnome-shell journald_cursor: s=e0727d9a8a414c4f8f45be933af8b75a;i=df3d;b=82bdfb5c47414607964bb78a6a9902c2;m=dcd37f3e;t=5831bf1d47d7a;x=728ccb02e83d9302 kernel: 4.20.10-200.fc29.x86_64 package: gnome-shell-3.30.2-1.fc29 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.