Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
On Sun, Oct 6, 2019 at 11:12 AM Michael Biebl wrote: > I'm still getting the fail-whale for the GNOME Classic session. > Tried with a fresh user account, just to be sure. > > Should this bug report be reopened or should I file a new one? Please file a new bug. smcv and I are thinking that gnome-session 3.34 may be required to finish up the big GNOME 3.34 transition. As bad as breaking GNOME Classic is, breaking all of GNOME in Testing ( https://bugs.debian.org/941782 ) is worse. So please file as Important and we can bump to Serious afterwards. I did confirm that I was unable to log in to GNOME Classic on Ubuntu 19.10 too. Ubuntu killed the fail whale, but it feels like the same bug to me. Thanks, Jeremy Bicha
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
I'm still getting the fail-whale for the GNOME Classic session. Tried with a fresh user account, just to be sure. Should this bug report be reopened or should I file a new one? signature.asc Description: OpenPGP digital signature
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
Control: reassign 940468 gnome-session Control: forcemerge 940468 -1 Hi, On Thu, Oct 03, 2019 at 02:16:32PM +0200, Michael Ott wrote: > Hi! > > I have the same problem. And I already create a bug report here > #940468 > > But I found out that it is a problem with mutter. > Using mutter 3.34.0-1 it works I'm not sure how mutter has anything to do with anything here, but your log also contains: Sep 16 07:52:31 k-c13 gnome-session-c[44308]: Failed to call signal initialization: GDBus.Error:org.gnome.SessionManager.GeneralError: Initialized interface is only available when gnome-session is managed by systemd Which means it's likely the same problem. Please be more specific about which actual session you're using in the future (and my recommendation would be to stay away from the "System X11 Default" one). Hopefully the just uploaded version should fix your problems. Regards, Andreas Henriksson
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
Hi! I have the same problem. And I already create a bug report here #940468 But I found out that it is a problem with mutter. Using mutter 3.34.0-1 it works CU Michael
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
On 2019-10-03 19:55, Andreas Henriksson wrote: So Gnome 3.34 is currently unusable. FWIW I have a hard time agreeing with this conclusion. One solution would be to simply drop support for "System X11 Default" which we're currently patching in. I'd say using it is not recommended and it only exists for legacy reasons. If you're using GNOME you should use either of the GNOME sessions and if not, then you should probably use something else than gdm. (And given this I don't think the current severity is warranted either.) Fair call, Gnome standard is fine (it also seemed to be failing when I first filed the bug, it must have cleared after reboot). Whether the bug severity should be downgraded depends I guess on how important the "Gnome classic" mode is. Drew
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong")
More tests: the failure occurs when logging in with "System X11 Default" or "Gnome Classic" selected from the gdm3 login screen. Log-in via the plain "Gnome" option does successfully start a gnome-session. Extensions from 3.30 cause it to freeze, but that's a separate issue (it works if extensions are disabled).
Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"
Package: gnome-session Version: 3.34.0-2 Severity: grave Justification: renders package unusable With the Gnome upgrade from 3.30 to 3.34, a Gnome session now fails to start. gdm3 runs fine, the login screen is shown and I can proceed with logging in. But instead of logging in and starting a session, it instead switches to a grey screen with the message "Oh no, something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." So Gnome 3.34 is currently unusable. This is with Gnome x11, not wayland. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-session depends on: ii gnome-session-bin 3.34.0-2 ii gnome-session-common 3.34.0-2 ii gnome-settings-daemon 3.34.0-3 ii gnome-shell3.34.0-2 gnome-session recommends no packages. Versions of packages gnome-session suggests: ii desktop-base 10.0.3 ii gnome-keyring 3.34.0-1 -- no debconf information
