Bug 1615135

Summary: [abrt] gnome-shell: gtk_action_observer_action_removed(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Erik Faye-Lund <kusmabite>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a81a3426604e261db5260f871fa6904d9794ac3b
Whiteboard: abrt_hash:e83077a947175bad07ec052c4995bfd2bd966402;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:42:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Erik Faye-Lund 2018-08-12 14:35:58 UTC
Description of problem:
Tried to open account sin Geary.

Version-Release number of selected component:
gnome-shell-3.28.1-2.fc28

Additional info:
reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gtk_action_observer_action_removed
executable:     /usr/bin/gnome-shell
journald_cursor: s=9baa3261cc754598af972600a2e1f8da;i=faeb;b=1c293eba45ef49aea5e2a54ff0a2cbcc;m=88a4745c6;t=5733dda60932a;x=e6bbb94ad592a884
kernel:         4.16.3-301.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 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:460
 #6 update_focus_app at ../src/shell-window-tracker.c:486

Comment 1 Erik Faye-Lund 2018-08-12 14:36:04 UTC
Created attachment 1475359 [details]
File: backtrace

Comment 2 Erik Faye-Lund 2018-08-12 14:36:05 UTC
Created attachment 1475360 [details]
File: cgroup

Comment 3 Erik Faye-Lund 2018-08-12 14:36:07 UTC
Created attachment 1475361 [details]
File: core_backtrace

Comment 4 Erik Faye-Lund 2018-08-12 14:36:08 UTC
Created attachment 1475362 [details]
File: cpuinfo

Comment 5 Erik Faye-Lund 2018-08-12 14:36:10 UTC
Created attachment 1475363 [details]
File: dso_list

Comment 6 Erik Faye-Lund 2018-08-12 14:36:12 UTC
Created attachment 1475364 [details]
File: environ

Comment 7 Erik Faye-Lund 2018-08-12 14:36:13 UTC
Created attachment 1475365 [details]
File: exploitable

Comment 8 Erik Faye-Lund 2018-08-12 14:36:14 UTC
Created attachment 1475366 [details]
File: limits

Comment 9 Erik Faye-Lund 2018-08-12 14:36:17 UTC
Created attachment 1475367 [details]
File: maps

Comment 10 Erik Faye-Lund 2018-08-12 14:36:18 UTC
Created attachment 1475368 [details]
File: mountinfo

Comment 11 Erik Faye-Lund 2018-08-12 14:36:19 UTC
Created attachment 1475369 [details]
File: open_fds

Comment 12 Erik Faye-Lund 2018-08-12 14:36:21 UTC
Created attachment 1475370 [details]
File: proc_pid_status

Comment 13 Erik Faye-Lund 2018-08-12 14:36:22 UTC
Created attachment 1475371 [details]
File: var_log_messages

Comment 14 Erik Faye-Lund 2018-10-02 10:56:24 UTC
Similar problem has been detected:

tried to open preferences in geary, then I got kicked out to the login screen while the "select audio device"-dialog popped up.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gtk_action_observer_action_removed
executable:     /usr/bin/gnome-shell
journald_cursor: s=84014a7675f24ef0b8abf203100d1ceb;i=a058;b=50be4788a69240009f0e4eab69ba5735;m=bc3d5f8cf;t=5773cba4626d7;x=66997fb85fc1e10d
kernel:         4.17.19-200.fc28.x86_64
package:        gnome-shell-3.28.3-1.fc28
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Ben Cotton 2019-05-02 20:45:58 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 16 Ben Cotton 2019-05-28 22:42:35 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.