GNOME Bugzilla – Bug 771985
Cannot login again after gnome session crashed
Last modified: 2021-06-14 18:21:33 UTC
After a gnome session crashed, logging in again often is not possible any more. Steps to reproduce: 1. log in into a gnome session (tested with wayland, dunno if X11 works the same) 2. Run into a gnome session crasher. Alternatively, you may press SAK (Alt+SysRq+K)¹ 3. try to login again What happens: You are immediately send back to gdm What should happen: Login should work fine, cleaning up stale processes if necessary. Additional info: Software always has bugs, but gnome-session should provide a way to recover from a broken session. I originally reported this in a comment on https://bugzilla.redhat.com/show_bug.cgi?id=1373169 but it looks like it doesn't fit in there. Both bugs might by related. Affected software versions (updated, then rebooted, then tested): gnome-shell 3.21.92-1.fc25 gdm 3.22.0-2.fc25 ¹ You'll probably have to press SAK twice due to another bug: https://bugzilla.gnome.org/show_bug.cgi?id=771548
I can confirm that this is still actively a bug. Distribution : Arch Linux (i believe the OP is on Fedora 25, i think this bug is independent of distribution and related to gnome-shell and GDM. Affected software versions : gnome-shell - 3.22.2+18+gdf7727a-1 GDM - 3.22.1 Steps to reproduce : 1. Logout of GNOME on Wayland session (default in most distributions now already) 2.)Try to login again (will get booted back to gdm in a second) 3. Only can login to this session again upon reboot Additional notes : 1. Locking the screen and logging in works fine 2. Choosing GNOME Classic or GNOME on Xorg/X11 works fine
I can confirm with the latest version. gnome-shell 3.22.2 GDM - 3.22.1 same symptoms. tty and x logins work as expected.
Here is the log of the re-login attempts from journalctl ------------------------------------------------------------------------------------------- Jan 04 18:32:25 yevsey systemd[1]: Starting GNOME Display Manager... Jan 04 18:32:25 yevsey systemd[1]: Started GNOME Display Manager. Jan 04 18:32:27 yevsey gdm[2010]: GdmDisplay: display lasted 0.352177 seconds Jan 04 18:33:16 yevsey gdm[2010]: GdmDisplay: display lasted 0.325071 seconds Jan 04 18:34:42 yevsey gdm[2010]: GdmDisplay: display lasted 0.321697 seconds Jan 04 18:36:24 yevsey gdm[2010]: Tried to look up non-existent conversation gdm-launch-environment Jan 04 18:36:24 yevsey gdm[2010]: Freeing conversation 'gdm-launch-environment' with active job Jan 04 18:36:24 yevsey gdm[2010]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus i Jan 04 18:36:24 yevsey gdm[2010]: GdmDisplay: display lasted 0.018844 seconds Jan 04 18:36:24 yevsey gdm[2010]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus i Jan 04 18:36:24 yevsey gdm[2010]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus i Jan 04 18:36:24 yevsey gdm[2010]: GdmDisplay: display lasted 0.000419 seconds Jan 04 18:36:24 yevsey gdm[2010]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus i Jan 04 18:36:24 yevsey systemd[1]: Stopping GNOME Display Manager... Jan 04 18:36:24 yevsey gdm[2010]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed Jan 04 18:36:24 yevsey systemd[1]: Stopped GNOME Display Manager. ------------------------------------------------------------------------
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of gnome-session, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-session/-/issues/ Thank you for your understanding and your help.