Fedora Workstation 35 - ''gnome-shell saiu inesperadamente''

Recebo essa mensagem sempre que inicio o sistema, o que pode ser?

var_log_messages
User Logs:
--abr 23 18:00:52 fedora gnome-shell[6579]: Running GNOME Shell (using mutter 41.0) as a Wayland display server
abr 23 18:00:52 fedora gnome-shell[6579]: Device '/dev/dri/card0' prefers shadow buffer
abr 23 18:00:52 fedora gnome-shell[6579]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
abr 23 18:00:52 fedora gnome-shell[6579]: Boot VGA GPU /dev/dri/card0 selected as primary
abr 23 18:00:53 fedora gnome-shell[6579]: Using public X11 display :0, (using :1 for managed services)
abr 23 18:00:53 fedora gnome-shell[6579]: Using Wayland display name 'wayland-0'
abr 23 18:00:53 fedora gnome-shell[6579]: Getting parental controls for user 1000
abr 23 18:00:53 fedora gnome-shell[6579]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
abr 23 18:00:53 fedora gnome-shell[6579]: Will monitor session 8
abr 23 18:00:53 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: firefox.desktop
abr 23 18:00:53 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Nautilus.desktop
abr 23 18:00:53 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Software.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: g_strsplit: assertion 'string != NULL' failed
abr 23 18:00:54 fedora gnome-shell[6579]: Telepathy is not available, chat integration will be disabled.
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: gnome-control-center.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Contacts.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Nautilus.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Boxes.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Calculator.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Calendar.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Characters.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: firefox.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Photos.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Software.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.clocks.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Terminal.desktop
abr 23 18:00:54 fedora gnome-shell[6579]: Some code accessed the property 'SecondaryMonitorDisplay' on the module 'workspacesView'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2cc70 StBin:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2abf0 Gjs_ui_panel_AppMenuButton.panel-button:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2de30 StBin:insensitive "appMenu" ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2eaa0 StBoxLayout.panel-status-menu-box:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc343c0 Gjs_ui_animation_Spinner:insensitive] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2cc70 StBin:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2abf0 Gjs_ui_panel_AppMenuButton.panel-button:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2de30 StBin:insensitive "appMenu" ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc2eaa0 StBoxLayout.panel-status-menu-box:insensitive ("")] which is not in the stage.
abr 23 18:00:55 fedora gnome-shell[6579]: st_widget_get_theme_node called on the widget [0x564f8cc343c0 Gjs_ui_animation_Spinner:insensitive] which is not in the stage.
abr 23 18:00:56 fedora gnome-shell[6579]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
abr 23 18:00:57 fedora gnome-shell[6579]: GNOME Shell started at Sat Apr 23 2022 18:00:54 GMT-0300 (Horário Padrão de Brasília)
abr 23 18:00:57 fedora gnome-shell[6579]: Registering session with GDM
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_remove: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_remove: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: meta_later_add: assertion 'display' failed
abr 23 18:03:12 fedora gnome-shell[6579]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed
abr 23 18:03:13 fedora gnome-shell[6579]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
[email protected]:///org/gnome/shell/ui/background.js:484:1
[email protected]:///org/gnome/shell/ui/background.js:508:14
[email protected]:///org/gnome/shell/ui/background.js:265:14
[email protected]:///org/gnome/shell/ui/background.js:592:30
[email protected]:///org/gnome/shell/ui/background.js:757:49
[email protected]:///org/gnome/shell/ui/background.js:688:37
[email protected]:///org/gnome/shell/ui/layout.js:433:25
[email protected]:///org/gnome/shell/ui/layout.js:477:34
[email protected]:///org/gnome/shell/ui/layout.js:539:14
[email protected]:///org/gnome/shell/ui/layout.js:294:14
[email protected]:///org/gnome/shell/ui/main.js:196:21
[email protected]:///org/gnome/shell/ui/main.js:162:5
@resource:///org/gnome/shell/ui/init.js:6:17
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
abr 23 18:03:13 fedora gnome-shell[6579]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x564f8cc2abf0.
abr 23 18:03:13 fedora gnome-shell[6579]: == Stack trace for context 0x564f8bca3190 ==
abr 23 18:03:13 fedora gnome-shell[6579]: == Stack trace for context 0x564f8bca3190 ==
abr 23 18:03:13 fedora gnome-shell[6579]: == Stack trace for context 0x564f8bca3190 ==
abr 23 18:03:13 fedora gnome-shell[6579]: == Stack trace for context 0x564f8bca3190 ==
abr 23 18:03:13 fedora gnome-shell[6579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
abr 23 18:03:13 fedora gnome-shell[6579]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x564f8cc2abf0.
abr 23 18:03:13 fedora gnome-shell[6579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
abr 23 18:03:13 fedora gnome-shell[6579]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x564f8cc2abf0.
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
abr 23 18:03:13 fedora gnome-shell[6579]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x564f8cc343c0.
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: instance of invalid non-instantiatable type '(null)'
abr 23 18:03:13 fedora gnome-shell[6579]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
abr 23 18:03:13 fedora gnome-shell[6579]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
--

Analisando aqui, está dizendo que a causa desse problema é:

gnome-shell killed by SIGSEGV

Isso não atrapalha em nada no funcionamento do sistema, apenas estou curioso para saber a causa dessa mensagem.

Inclusive, estou tentando reportar isso e não consigo:

--- Running report_uReport ---
('report_uReport' concluído com sucesso)

---Ignorando collect_vimrc_system ---
Não foram encontradas ações correspondentes a esse evento.

---Ignorando collect_vimrc_user ---
Não foram encontradas ações correspondentes a esse evento.

---Ignorando collect_xsession_errors ---
Não foram encontradas ações correspondentes a esse evento.

---Ignorando collect_GConf ---
Não foram encontradas ações correspondentes a esse evento.

--- Running analyze_CCpp ---
Carregar dump central? (Pode conter dados sensíveis). Se a resposta for 'Não', um rastreamento em pilha será gerado localmente. (Pode baixar uma grande quantidade de dados). 'YES'
Consultando configurações do servidor
Preparando um arquivo para fazer upload
Você vai carregar 14,4 MiB. Continuar? 'YES'
Fazendo upload 14,4 MiB
Upload realizado com sucesso
Retrace job #417993403 started
Retrace job finished successfully
O servidor de retraçamento falhou. Tente novamente mais tarde e se o problema persistir, por favor reporte o problema.
[2022-04-24 01:03:39] [I] Analyzing crash data

Você deseja gerar um rastreamento em pilha localmente? (Pode baixar uma grade quantidade de dados mas a reportagem não pode continuar sem o rastreamento em pilha). 'NO'
('analyze_CCpp' saiu com 1)


@moderadores Solicito a exclusão do tópico. Ativei o inicio automático de sessão e a mensagem desapareceu.