[Gnome Shell/Libsoup] white "Oh no!" screen after update F37

Yesterday updated my F37 system via the “GNOME Software” App.
Packages were downloaded & the system rebooted to install the new packages. After everything was done i was greeted with a white screen saying “Oh no! Something has gone wrong”.

I check for new updates every 1-2 weeks and apply them within 2-3 days, so the delta is usually pretty small. We are not talking about a “i have not updated my system for half a year”.
I remember that the update contained a few gnome packages but i can’t exactly tell which.

I tried to verify if this is a partial-update situation so i started with
dnf distro-sync --releasever=37
but everything was fine. So i tried to check again via

> dnf check-update

Last metadata expiration check: 1:20:28 ago on Fri 20 Jan 2023 07:22:20 AM CET.

curl.x86_64                             7.85.0-5.fc37                    updates
libcurl.x86_64                          7.85.0-5.fc37                    updates
libcurl-devel.x86_64                    7.85.0-5.fc37                    updates
> dnf update

Last metadata expiration check: 1:24:30 ago on Fri 20 Jan 2023 07:22:20 AM CET.
Dependencies resolved.

 Problem 1: package libcurl-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64) >= 1.51.0, but none of the providers can be installed
  - cannot install the best update candidate for package libcurl-7.85.0-1.fc37.x86_64
  - package libnghttp2-1.51.0-1.fc37.x86_64 is filtered out by modular filtering
 Problem 2: package curl-7.85.0-5.fc37.x86_64 requires libcurl(x86-64) >= 7.85.0-5.fc37, but none of the providers can be installed
  - package libcurl-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64) >= 1.51.0, but none of the providers can be installed
  - package libcurl-minimal-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64) >= 1.51.0, but none of the providers can be installed
  - cannot install the best update candidate for package curl-7.85.0-1.fc37.x86_64
  - package libnghttp2-1.51.0-1.fc37.x86_64 is filtered out by modular filtering
 Problem 3: package libcurl-devel-7.85.0-5.fc37.x86_64 requires libcurl(x86-64) = 7.85.0-5.fc37, but none of the providers can be installed
  - package libcurl-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64) >= 1.51.0, but none of the providers can be installed
  - package libcurl-minimal-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64) >= 1.51.0, but none of the providers can be installed
  - cannot install the best update candidate for package libcurl-devel-7.85.0-1.fc37.x86_64
  - package libnghttp2-1.51.0-1.fc37.x86_64 is filtered out by modular filtering
================================================================================
 Package                Architecture  Version              Repository      Size
================================================================================
Skipping packages with broken dependencies:
 curl                   x86_64        7.85.0-5.fc37        updates        316 k
 libcurl                x86_64        7.85.0-5.fc37        updates        304 k
 libcurl-devel          x86_64        7.85.0-5.fc37        updates        977 k
 libcurl-minimal        x86_64        7.85.0-5.fc37        updates        239 k

Transaction Summary
================================================================================
Skip  4 Packages

Nothing to do.
Complete!

Doesn’t look too bad imho.

Other discussions on ask.fedoraproject have also recommended to switch from Wayland to X11 via editing gdm’s custom.conf. I have ditched Wayland from my first installation of this system ~2 years ago after i had problems when screen sharing via skype, teams etc.

Here is the journalctl -xb -r (the following output is thus reversed!). The journal proves that i’m using X11 and shows some errors.

Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1852]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1728]: dbus-daemon[1728]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 20 08:40:14 probook audit: BPF prog-id=87 op=LOAD
Jan 20 08:40:14 probook audit: BPF prog-id=86 op=LOAD
Jan 20 08:40:14 probook audit: BPF prog-id=85 op=LOAD
Jan 20 08:40:14 probook kernel: rfkill: input handler disabled
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1728]: dbus-daemon[1728]: Activating service name='org.a11y.atspi.Registry' requested by ':1.4' (uid=42 pid=1803 comm="/usr/libexec/gsd-keyboard" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 20 08:40:14 probook gnome-session-binary[1713]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Datetime.desktop
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' respawning too quickly
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' respawning too quickly
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' exited with code 127
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' exited with code 127
Jan 20 08:40:14 probook org.gnome.SettingsDaemon.Datetime.desktop[1828]: /usr/libexec/gsd-datetime: symbol lookup error: /lib64/libsoup-3.0.so.0: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' exited with code 127
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.SettingsDaemon.Datetime.desktop' exited with code 127
Jan 20 08:40:14 probook org.gnome.SettingsDaemon.Datetime.desktop[1811]: /usr/libexec/gsd-datetime: symbol lookup error: /lib64/libsoup-3.0.so.0: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1712]: dbus-daemon[1712]: [session uid=42 pid=1712] Successfully activated service 'ca.desrt.dconf'
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1712]: dbus-daemon[1712]: [session uid=42 pid=1712] Activating service name='ca.desrt.dconf' requested by ':1.4' (uid=42 pid=1713 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 20 08:40:14 probook gnome-session-binary[1713]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 20 08:40:14 probook gnome-shell[1767]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Jan 20 08:40:14 probook gnome-shell[1767]: JS ERROR: Error: Unsupported type void, deriving from fundamental void
                                           @resource:///org/gnome/shell/ui/extensionDownloader.js:13:1
                                           @resource:///org/gnome/shell/ui/extensionSystem.js:7:29
                                           @resource:///org/gnome/shell/ui/main.js:19:25
                                           @resource:///org/gnome/shell/ui/init.js:6:1
Jan 20 08:40:14 probook gnome-shell[1767]: Failed to load shared library 'libsoup-3.0.so.0' referenced by the typelib: /lib64/libsoup-3.0.so.0: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Jan 20 08:40:14 probook gnome-shell[1767]: ATK Bridge is disabled but a11y has already been enabled.
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Modeline "1920x1080"x0.0   95.16  1920 1968 2000 2124  1080 1083 1089 1120 +hsync -vsync (44.8 kHz e)
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  142.74  1920 1968 2000 2124  1080 1083 1089 1120 +hsync -vsync (67.2 kHz eP)
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Printing DDC gathered Modelines:
Jan 20 08:40:14 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): EDID vendor "BOE", prod id 2152
Jan 20 08:40:14 probook gnome-shell[1767]: Running GNOME Shell (using mutter 43.2) as a X11 window and compositing manager
Jan 20 08:40:14 probook gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 20 08:40:14 probook gnome-session[1713]: gnome-session-binary[1713]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 20 08:40:14 probook gnome-shell[1740]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Jan 20 08:40:14 probook gnome-shell[1740]: JS ERROR: Error: Unsupported type void, deriving from fundamental void
                                           @resource:///org/gnome/shell/ui/extensionDownloader.js:13:1
                                           @resource:///org/gnome/shell/ui/extensionSystem.js:7:29
                                           @resource:///org/gnome/shell/ui/main.js:19:25
                                           @resource:///org/gnome/shell/ui/init.js:6:1
Jan 20 08:40:14 probook gnome-shell[1740]: Failed to load shared library 'libsoup-3.0.so.0' referenced by the typelib: /lib64/libsoup-3.0.so.0: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Jan 20 08:40:14 probook gnome-shell[1740]: ATK Bridge is disabled but a11y has already been enabled.
Jan 20 08:40:13 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Modeline "1920x1080"x0.0   95.16  1920 1968 2000 2124  1080 1083 1089 1120 +hsync -vsync (44.8 kHz e)
Jan 20 08:40:13 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  142.74  1920 1968 2000 2124  1080 1083 1089 1120 +hsync -vsync (67.2 kHz eP)
Jan 20 08:40:13 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): Printing DDC gathered Modelines:
Jan 20 08:40:13 probook /usr/libexec/gdm-x-session[1696]: (II) AMDGPU(0): EDID vendor "BOE", prod id 2152
Jan 20 08:40:13 probook gnome-shell[1740]: Running GNOME Shell (using mutter 43.2) as a X11 window and compositing manager

I think the problem is pretty obvious know, it is either libsoup or the gnome-shell javascript files.

What can i do from here?
Is there a way to see which packages have been updated most recently?
Is there a way to rollback some of those packages and explicitly install the old versions?

Is it a coincidence that the dnf update yields

Problem 1: package libcurl-7.85.0-5.fc37.x86_64 requires libnghttp2(x86-64)

and that the libsoup error in the journal also points to some nghttp2 stuff?

Jan 20 08:40:14 probook gnome-shell[1767]: Failed to load shared library 'libsoup-3.0.so.0' referenced by the typelib: /lib64/libsoup-3.0.so.0: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation

Same here! Logging in with Ctrl alt f4 and doing
Sudo dnf update
has not helped me get back into a graphical environment so far.

Also have a curl/libcurl conflict

Looks like we’re in the same boat. I would have thought this is a unique problem for my setup.
What does your journal say? Do you get similar gnome-shell/libsoup logs?

I had a very similar situation, it turns out my problem was fixed by removing nodejs and resetting its module.
I ran dnf module provides libnghttp2, which told me that it came from nodejs:14.
I then ran dnf remove nodejs, dnf module reset nodejs and dnf check-update; at this point I saw the curl/libcurl updates as well as a new nodejs update to stream 18 (which seems to be the default in Fedora 37).
I ran dnf update and then reboot and now everything works

5 Likes

You are a Linux god!!! Thanks so much for this - this saved me from a full reinstall. I had node installed, followed your commands and now see GDM again.

This has not been an issue for 2 years. Strange - my first breakage ever on Fedora. Anyway thanks again! Now I can get on my video meeting in time….so maybe I shouldn’t have fixed it!

Thanks Luca… you saved my day!

For anyone running into the same situation and wondering how to get to a shell from the “Oh no! Something has gone wrong” screen: ctrl+alt+F2 to get to a text console.

In my case I’ve already been running Fedora 37 for a while. The error seemed to just suddenly appear (maybe some gnome extension that updated and failed with the old nodejs version?).
In journalctl I found some JS errors similar (but different than) the OP had. In my case I was using the default Wayland.