Context (off topic):
State of tumbleweed looks a little under stress recently … After an update on Sept 25 the gdm graphical login crashed. Going to an older kernel did not help. In the process of going after this, I tried a distribution update, which did not help either. I could fix this only following the hack here:
And now everything is up and running and seemingly fine, if it wasn’t that nautilus (aka Files) crashes again and again after using it for a while going back and forth between some directories. Invoking it again it is up fine again for a while. Crashing is not reliably reproducible as far as I can tell. It seems not to destroy anything in the process. Looks like only the window crashes.
Not sure how to tell journalctl only to give me the latest of these tons of nautilus related messages.
But given the context above I am reluctant “to go back” in the installation history. I can live with it for the moment, but I am curious if others observe this, too.
The graphical login issue was probably caused by this bug, which means users should try the workaround mentioned in the bug report first before following the steps from Arch Linux Forums. I know those are also a good source for information, but in this case you should make sure GDM can use its dynamic user correctly.
No problems here and I don’t understand what “the hack here” means (you linked a full page with mostly unrelated comments?)
GDM only uses Wayland on Gnome 49 so if you used X11 sessions you had to adjust for that.
And if you are one of those affected by the dynamic users problem follow what @mendres82 wrote.
That’s a post that suggests adding a line for gdm-greeter to /etc/shadow to fix the gdm login screen.
@mendres82 I followed the link to the bug list, read through, came to the conclusion that Comment 21 was the proposed solution, applied it, took out the line for gdm-greeter from /etc/shadow, rebooted and got a broken graphical login. So I added the gdm-greeter line again to /etc/shadow to get my desktop and to post a reply here.
The reason I ended up in the arch-linux forum was just that I did not find anything here for opensuse (given my search terms). And I am a user of opensuse tumbleweed (and leap on another computer), not a operating system or application developer. So I am not usually following these bug list sites.
What leaves me puzzled is that I seem only to find lists of hacks and workarounds of (apparently?) non-gnome developers. What is the “officially” proposed system setup for this to work? From the lack of posts here I conclude that not many, if any, faced the login issue. I thought my setup was standard. I guess I have to rely on future updates and check from time to time when I can remove the line from /etc/shadow …
The proposed solution is comment 2, but please don‘t just delete the file. Make sure the lines beginning with passwd, group, shadow contain a systemd entry.