Created attachment 1861299 [details] system log Description of problem: Updating gnome-shell to 42~beta-1.fc37 or mutter to 42~beta-1.fc37 version breaks the login screen. Instead of login screen I see "Oh no! Something has gone wrong". In the system log I see this messages: Feb 15 20:57:41 mikhail-laptop gnome-shell[1291]: Running GNOME Shell (using mutter 42.beta) as a Wayland display server Feb 15 20:57:41 mikhail-laptop gnome-shell[1291]: Device '/dev/dri/card1' prefers shadow buffer Feb 15 20:57:41 mikhail-laptop gnome-shell[1291]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Feb 15 20:57:41 mikhail-laptop gnome-shell[1291]: Device '/dev/dri/card2' prefers shadow buffer Feb 15 20:57:41 mikhail-laptop gnome-shell[1291]: Added device '/dev/dri/card2' (amdgpu) using atomic mode setting. Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Created gbm renderer for '/dev/dri/card1' Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Created gbm renderer for '/dev/dri/card2' Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Boot VGA GPU /dev/dri/card2 selected as primary Feb 15 20:57:42 mikhail-laptop /usr/libexec/gdm-wayland-session[1282]: dbus-daemon[1282]: [session uid=42 pid=1282] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=42 pid=1291 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Feb 15 20:57:42 mikhail-laptop /usr/libexec/gdm-wayland-session[1282]: dbus-daemon[1282]: [session uid=42 pid=1282] Successfully activated service 'org.a11y.Bus' Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Using public X11 display :1024, (using :1025 for managed services) Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Using Wayland display name 'wayland-0' Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: JS ERROR: Error: [GObject prototype of GIName:Gio.DataInputStream jsobj@0x91c947ace50] has no method named undefined _promisify@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:411:15 @resource:///org/gnome/shell/ui/environment.js:31:5 @resource:///org/gnome/shell/ui/init.js:5:1 Feb 15 20:57:42 mikhail-laptop gnome-shell[1291]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception Feb 15 20:57:42 mikhail-laptop gnome-session[1283]: gnome-session-binary[1283]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Feb 15 20:57:42 mikhail-laptop gnome-session-binary[1283]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Feb 15 20:57:42 mikhail-laptop gnome-session-binary[1283]: Unrecoverable failure in required component org.gnome.Shell.desktop Feb 15 20:57:42 mikhail-laptop /usr/libexec/gdm-wayland-session[1282]: dbus-daemon[1282]: [session uid=42 pid=1282] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=42 pid=1283 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Feb 15 20:57:42 mikhail-laptop org.gnome.Shell.desktop[1361]: (EE) could not connect to wayland server Feb 15 20:57:42 mikhail-laptop /usr/libexec/gdm-wayland-session[1282]: dbus-daemon[1282]: [session uid=42 pid=1282] Successfully activated service 'ca.desrt.dconf' Feb 15 20:57:42 mikhail-laptop gdm-launch-environment][1243]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Proposed as a Blocker and Freeze Exception for 36-beta by Fedora user mikhail using the blocker tracking app because: It a major issue because I can not login into the gnome.
I suspect this probably needs gjs 1.71.1, which was tagged a day ago upstream, not yet built for Fedora. Commits to `environment.js` in gnome-shell say things like "gjs now supports overriding interface methods, so promisify() works on Gio.File itself, not just the LocalFilePrototype cludge."
And yeah, I see this in the 1.71.1 change notes upstream: - It's now possible to monkeypatch methods on the prototype of a GObject interface. The most common use case for this is probably promisifying methods on `Gio.File`, so you can now do things like `Gio._promisify(Gio.File.prototype, 'read_async')` without resorting to the `Gio._LocalFilePrototype` workaround.
Why this issue not catched by automated QA tests? `$ koji download-build gjs-1.71.1-1.fc37 --arch=x86_64 --arch=noarch` helps me.
Well, it was: https://openqa.fedoraproject.org/tests/1130223 but those tests run on the compose, so after the builds landed. We don't currently test Rawhide updates in openQA. I'm working on doing that this year, but it takes quite a bit of groundwork to prepare.
This should be good with all current builds. Note they won't be in official Rawhide repo yet as we don't have a successful compose yet, but if you update from the koji repo it should be good. I'm running f36-gnome packages on F36 (same set of builds), and GNOME is OK.
openQA confirms this is fixed now.