Bug 1956938

Summary: [abrt] gnome-shell: _clutter_actor_get_stage_internal(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Riyad Kalla <rkalla>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: fmuellner, gnome-sig, jadahl, otaylor, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/195873864014ab4c43b81c3e94516f5128e4e229
Whiteboard: abrt_hash:b687071d4d902b0d0db0fafa27c082d47a2d9b81;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 21:15:22 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: 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 Riyad Kalla 2021-05-04 17:28:51 UTC 
Description of problem:
No particular action - was simply using gnome and alt-tabbed back to a window and the shell closed and immediately re-started - like explorer.exe crashing on Windows.

Didn't interrupt my work much so great recovery there!

Version-Release number of selected component:
gnome-shell-40.0-6.fc34

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: _clutter_actor_get_stage_internal
executable:     /usr/bin/gnome-shell
journald_cursor: s=66a2e3896c8341fa9b9bcef0d74de852;i=6b4be;b=0983f1fa6b45465eb36bd1949fc82fb1;m=1082efc95c;t=5c18316243d71;x=2bd9815e4a814656
kernel:         5.11.17-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 0 (10 frames)
 #0 _clutter_actor_get_stage_internal at ../clutter/clutter/clutter-actor.c:13546
 #1 clutter_actor_unrealize_not_hiding at ../clutter/clutter/clutter-actor.c:2153
 #2 clutter_actor_update_map_state at ../clutter/clutter/clutter-actor.c:1462
 #3 clutter_actor_remove_child_internal at ../clutter/clutter/clutter-actor.c:4220
 #4 st_bin_set_child at ../src/st/st-bin.c:375
 #5 clutter_actor_dispose at ../clutter/clutter/clutter-actor.c:5529
 #7 clutter_actor_destroy at ../clutter/clutter/clutter-actor.c:7978
 #8 st_bin_destroy at ../src/st/st-bin.c:205
 #13 clutter_actor_dispose at ../clutter/clutter/clutter-actor.c:5523
 #14 st_widget_dispose at ../src/st/st-widget.c:334
Comment 1 Riyad Kalla 2021-05-04 17:28:54 UTC 
Created attachment 1779449 [details]
File: backtrace
Comment 2 Riyad Kalla 2021-05-04 17:28:54 UTC 
Created attachment 1779450 [details]
File: core_backtrace
Comment 3 Riyad Kalla 2021-05-04 17:28:55 UTC 
Created attachment 1779451 [details]
File: cpuinfo
Comment 4 Riyad Kalla 2021-05-04 17:28:56 UTC 
Created attachment 1779452 [details]
File: dso_list
Comment 5 Riyad Kalla 2021-05-04 17:28:57 UTC 
Created attachment 1779453 [details]
File: environ
Comment 6 Riyad Kalla 2021-05-04 17:28:58 UTC 
Created attachment 1779454 [details]
File: exploitable
Comment 7 Riyad Kalla 2021-05-04 17:28:59 UTC 
Created attachment 1779455 [details]
File: limits
Comment 8 Riyad Kalla 2021-05-04 17:28:59 UTC 
Created attachment 1779456 [details]
File: maps
Comment 9 Riyad Kalla 2021-05-04 17:29:00 UTC 
Created attachment 1779457 [details]
File: mountinfo
Comment 10 Riyad Kalla 2021-05-04 17:29:01 UTC 
Created attachment 1779458 [details]
File: open_fds
Comment 11 Riyad Kalla 2021-05-04 17:29:01 UTC 
Created attachment 1779459 [details]
File: proc_pid_status
Comment 12 Riyad Kalla 2021-05-04 17:29:02 UTC 
Created attachment 1779460 [details]
File: var_log_messages
Comment 13 Ben Cotton 2022-05-12 15:17:09 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 14 Ben Cotton 2022-06-07 21:15:22 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

Thank you for reporting this bug and we are sorry it could not be fixed.