libsoup3 breaks gjs/gnome-shell
Feb 26 02:26:53 slimbook gnome-shell[898]: JS ERROR: Error: No property ssl_use_system_ca_file on SoupSession
init@resource:///org/gnome/shell/ui/extensionDownloader.js:243:20
_initializeUI@resource:///org/gnome/shell/ui/main.js:277:25
start@resource:///org/gnome/shell/ui/main.js:169:5
@<main>:1:47
Feb 26 02:26:53 slimbook gnome-shell[898]: Execution of main.js threw exception: Script <main> threw an exception
Feb 26 02:26:53 slimbook gnome-shell[1002]: could not connect to wayland server
Feb 26 02:26:53 slimbook gnome-shell[1002]: (EE)
Feb 26 02:26:53 slimbook gnome-shell[1002]: Fatal server error:
Feb 26 02:26:53 slimbook gnome-shell[1002]: (EE) Couldn't add screen
Feb 26 02:26:53 slimbook gnome-shell[1002]: (EE)
Looks like gjs bindings for "Soup" now point to soup3 and it breaks existing users. Removing soup3 from the runtime seems to indeed workaround it and get the shell to launch again.