Gnome-shell crashes with new Slowroll update

English Applications
1

Getting error:

Oct 10 09:05:09 suse-pc gnome-shell[2946]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate g_settings_bind_with_mapping_closures: 'g_settings_bind_with_mapping_closures': /lib64/libgio-2.0.so.0: undefined symbol: g_settings_bind_with_mapping_closures
                                           _init@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:725:50
                                           require@resource:///org/gnome/gjs/modules/esm/gi.js:16:28
                                           @gi://Gio/:3:25
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception

Looks like an incompatible libgio library issue. Any ideas on a fix? :thinking:

Full log:

pavin@suse-pc:~> journalctl --user -b -4 -u org.gnome.Shell@wayland.service | cat
Oct 10 09:05:09 suse-pc systemd[2680]: Starting GNOME Shell on Wayland...
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Running GNOME Shell (using mutter 46.5) as a Wayland display server
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Device '/dev/dri/card1' prefers shadow buffer
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Created gbm renderer for '/dev/dri/card1'
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Boot VGA GPU /dev/dri/card1 selected as primary
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Obtained a high priority EGL context
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Obtained a high priority EGL context
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Using public X11 display :0, (using :1 for managed services)
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Using Wayland display name 'wayland-0'
Oct 10 09:05:09 suse-pc gnome-shell[2946]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate g_settings_bind_with_mapping_closures: 'g_settings_bind_with_mapping_closures': /lib64/libgio-2.0.so.0: undefined symbol: g_settings_bind_with_mapping_closures
                                           _init@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:725:50
                                           require@resource:///org/gnome/gjs/modules/esm/gi.js:16:28
                                           @gi://Gio/:3:25
Oct 10 09:05:09 suse-pc gnome-shell[2946]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Oct 10 09:05:10 suse-pc systemd[2680]: org.gnome.Shell@wayland.service: Failed with result 'protocol'.
Oct 10 09:05:10 suse-pc systemd[2680]: Failed to start GNOME Shell on Wayland.
Oct 10 09:05:10 suse-pc systemd[2680]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Oct 10 09:05:10 suse-pc systemd[2680]: org.gnome.Shell@wayland.service: Consumed 363ms CPU time, 185.8M memory peak.
Oct 10 09:05:11 suse-pc systemd[2680]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
Oct 10 09:05:19 suse-pc systemd[2680]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
Oct 10 09:05:25 suse-pc systemd[2680]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
1 Like
2

Looks like a bad update, issues with multiple libraries (missing symbol errors):

  • typelib-1_0-Gio-2_0 causes DE crash (wayland and x11)
  • libgoa-backend-1_0-2 causes gnome-control-center to not work

Locking the following packages and upgrading seems to work:

libgoa-backend-1_0-2
typelib-1_0-Gio-2_0
2 Likes
3

Additionally locked and downgraded these packages due to issues reported by other users:

libgiomm-2_68-1
libgio-2_0-0
4

Another one I found from past logs due to the same issue (now solved!):

Oct 14 03:07:36 suse-pc atomic-update[342567]: flatpak: symbol lookup error: /lib64/libgobject-2.0.so.0: undefined symbol: g_sort_array

Does anyone know of a way to detect these undefined symbols in shared libraries? :thinking:
That would be very helpful in preventing a faulty update from being applied. :stop_sign:

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.