After gnome (?) update stuck in a login loop

After (presumably) the Gnome 50 update I am stuck in a login loop at my login screen. (Presumably because there also have been other updates, so can’t be 100% sure.) I am using opensuse tumbleweed.

For now I reverted back to an old snapshot from yesterday and everything is working as expected, but these are the things I found out while being stuck in the broken system:

The main error I could identify is:

Apr 13 07:31:19 nyy gnome-session-i[3979]: A graphical session is already running!
Apr 13 07:31:19 nyy systemd-coredump[4409]: [🡕] Process 3979 (gnome-session-i) of user 1000 dumped core.

When I logged into tty and ran loginctl list-sessions I could always see myself, gdm-greeter and a “manager”. Not sure if the manager shouldve run? I killed my session in various ways but still this error fired every time I tried to log in.

gnome-session --wayland works and I can see all the new gnome features in there, but from there I can’t log out and in the list-session it still listed this as a tty session.

I also tried disabling all my extensions and even deleted all my gnome settings, both things didn’t help.

Something weird in your setup, that command spits out a “Unknown option --wayland” and aborts with a core dump here (with i+ | gnome-session | package | 50.0-1.1 | x86_64 | repo-oss).
So check that you are using gdm as display manager, that it is upgraded to 50, that you choose “gnome” at the login screen (and not some remnant from previous installs) and remember that Gnome 50 completely abandoned X11, so if you have old configs or sessions around (possibly locked?) try to clear them.

EDIT: and maybe try gnome-session-quit if you cannot kill that odd session.

1 Like

@nyy also how are you upgrading the system? Likewise, I would suggest switching to a tty, log in as root user, run systemctl isolate multi-user.target then run zypper -vvv dup then reboot.

To add the logout option in GNOME 50, as your user run gsettings set org.gnome.shell always-show-log-out true

1 Like

I upgraded with sudo zypper dup

I tried this inside tty, but still the same issue after rebooting.

How can I check that? When I check systemctl status display-manager it says gdm.service

So in the gdm login screen you should still be able to choose icewm for a minimal desktop (check the cog wheel in the lower right corner), then check and post here:

zypper se -si gdm gnome-shell gnome-session mutter
S  | Name                                         | Type    | Version      | Arch   | Repository
---+----------------------------------------------+---------+--------------+--------+----------------------
i  | gdm                                          | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gdm-branding-openSUSE                        | package | 15.1-3.7     | noarch | Main Repository (OSS)
i  | gdm-schema                                   | package | 50.0-1.1     | noarch | Main Repository (OSS)
i+ | gdm-systemd                                  | package | 50.0-1.1     | noarch | Main Repository (OSS)
i  | gdm-xdm-integration                          | package | 50.0-1.1     | noarch | Main Repository (OSS)
i+ | gnome-session                                | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gnome-shell                                  | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gnome-shell-calendar                         | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gnome-shell-search-provider-contacts         | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gnome-shell-search-provider-gnome-calculator | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | gnome-shell-search-provider-gnome-characters | package | 50.0-1.1     | noarch | Main Repository (OSS)
i  | gnome-shell-search-provider-gnome-clocks     | package | 50.0-1.1     | noarch | Main Repository (OSS)
i  | gnome-shell-search-provider-gnome-photos     | package | 44.0+23-3.3  | noarch | Main Repository (OSS)
i  | gnome-shell-search-provider-gnome-weather    | package | 50.0-1.1     | noarch | Main Repository (OSS)
i  | gnome-shell-search-provider-nautilus         | package | 50.0-1.1     | noarch | Main Repository (OSS)
i  | gnome-shell-search-provider-seahorse         | package | 47.0.1+6-3.1 | noarch | Main Repository (OSS)
i  | libgdm1                                      | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | mutter                                       | package | 50.0-1.1     | x86_64 | Main Repository (OSS)
i  | typelib-1_0-Gdm-1_0                          | package | 50.0-1.1     | x86_64 | Main Repository (OSS)

Looks good…
Are there other users and can they login? Or can you create a fresh user and check?

Also, do you have an /etc/gdm/custom.conf file? If so, please post cat /etc/gdm/custom.conf

# GDM configuration storage
#
# Note: settings from /etc/sysconfig/displaymanager have a higher priority
#

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

Will try adding a new user now!

The fresh user can login without problems. So it must be something with my user…

Something in ~/.config/gnome-session/saved-session?

bash: cd: /home/nyy/.config/gnome-session/saved-session: No such file or directory

No old extensions? Maybe just comparing the configs for the old and new user shows something interesting? Starting with ~/.profile and ~/.ICEauthority ?

The profile is almost the same, the one on my original user just has the things to get pyenv working… I commented it out just in case, but still can’t login. I can’t find any ~/.ICEauthority file on either account.

Did you reboot without logging out? Is there still a .lock file or similar?
Any autostart app that might no longer be there?

Hmm, I am not sure. Where would I check for the .lock file?

I randomly looked around and stumbled upon this, could any of this be an issue?

/run/user/1000/pipewire-0-manager.lock
/run/user/1000/pipewire-0.lock
find: ‘/run/user/1000/gvfs’: Permission denied
find: ‘/run/user/1000/doc’: Permission denied

If user 1000 is currently logged in you should also see something like:

wayland-0.lock
.mutter-Xwaylandauth.xxxx

if user 1000 is currently not logged in the directory /run/user/1000/ should not exist and that would definitely be a problem.

I renamed my config folder to back it up and let the system create a new one… and… I can now login again…! To this new folder, I copied over most of my old configs again that I feel like I need and everything still works. I have no idea what the issue was but it seems like it works now. Thanks for the help and the troubleshooting!

1 Like

Nice to see you are in business again, meanwhile I was looking at ~/.config/dconf/user which could store old tweaks that no longer apply to the new wayland-only Gnome…
But my last resort was exactly what you did. Just keep that backup around, just in case :wink:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.