No longer able to reach gnome login screen after latest update

English Install/Boot/Login
1

Hello,

as the title states I can’t log in anymore after the latest tumbleweed update. What I see:

  1. Tumbleweed splash screen shows up
  2. A loading indicator is visible for a short time
  3. It hangs (normally I should see the login screen now)

I don’t see any error messages besides

ACPI BIOS Error (bug): Failure creating named object AE_ALREADY_EXISTS
ACPI Error : AE_ALREADY_EXISTS, During name lookup/catalog 
amdgpu 0000:83:00.0: amdgpu psq req (0x16063) wait timed

But after searching for these errors the consensus seems to be that those can be safely ignored.

Desktop environment is Gnome. I have a laptop with AMD CPU with integrated graphics. (I can find out the exact specs if necessary)

I’m not sure where to start debugging this. Any help is appreciated

1 Like
2

Also, booting from the previous kernel does not help.

Previous kernel is 6.16.7-1 (used to work)

Current kernel is 6.16.8-1

3

I also updated flatpak, there was some Gnome 49 stuff in there. More likely that that is the problem?

4

Removed Gnome 49 (and dependent packages). Didn’t help

5

@wor404 Hi, not seeing that here, but I don’t run Plymouth either. I would suggest a bug report is in order https://en.opensuse.org/openSUSE:Submitting_bug_reports

6

Just a wild guess according to https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/33VV7VJOIDETPPZZEGKXDXCNXH3OUQ5D/: “GNOME 49: Upgraders might run into an issue with dynamic user generation. The issue does not originate from GNOME, but rather /etc/nsswitch.conf not having nss-systemd registered for passwd/group and shadow. See 1250513 – [Build 20250924] Upgrades from 15.x seem to get the config for gdm / dynamic user generation wrong if you are affected, and a workaround. We are looking into ways to fix this automatically.”

2 Likes
7

Thanks! Will try the workaround tomorrow and report a bug if it doesn’t work

8

Thank you for pointing us to this bug report and its workaround.

Applying the workaround in the recovery mode fixed my system:

rm /etc/nsswitch.conf
poweroff
1 Like
9

I have the exact same Problem.
Zypper dup installed Gnome 49.
After a reboot the same thing you explained happens. Also no chance with the snapshot of the older Kernel.

10

Can confirm that renaming or removing /etc/nsswitch.conffixed the problem.

On a side note, upgrading to Gnome 49 currently breaks PaperWM

11

Looks like I’m still on Gnome 48 - so a bit worried / reluctant about doing the next dup on my Tumbleweed system. Does anyone know if I could run the suggested work around rm /etc/nsswitch.conf poweroffthat seems to have worked for others BEFORE doing dup to head it off at the pass as it were & maybe without the poweroff.
Or do we think this will be sorted in the next few days?

12

Can confirm that renaming or removing /etc/nsswitch.conffixed the problem.

For me, it did not solve the issue, it made it worse.

13

Then you have most likely a different problem

14

I’d run the workaround after the zypper dup and before the next boot.

Possibly, watch the bug report linked above.

1 Like
15

Then you have most likely a different problem

The fact that something helps you doesn’t imply that it helps everybody.

But yes, I had another problem on top of this one. My “problem” was that I’m using LDAP and sssd. I had to modify my PAM configuration. Without that, the gdm_greeter user would be accepted by the system. See other thread for details.

16

Sorry but I am not a tech guy.
My Laptop is affected and I don’t know how I can do a workaround if it doesn’t start.

And if there is a fix coming with an update how would I be able to update?

Any help is recommended. Worst case is to make a new install. But my Tumbleweed was running for 3 years now without any Problem and it took me forever to delete and block all the stuff I don’t need.

17

Do you know what the boot menu is?
When the system starts, before you see the openSUSE logo, there is a black screen with a few (likely: four) lines of white text. It is shown for a few seconds.
With the down-arrow key, select the advanced options. It’s likely the second line. Press Enter.
Then go to the first line which contains “(Recovery mode)”. It’s also likely the second line. Press Enter.

The system will boot and then ask you for the Root password. Enter it.
Then enter:

rm /etc/nsswitch.conf
poweroff

(I’m assuming that you have no special configuration in that file, given that you are “not a tech guy” ;))
Then switch the system on and it should work.

1 Like
18

Thank you thank you thank you :grin:
That worked.
What didn’t work is “poweroff” but ctrl+alt+del rebooted the computer and I was able to just boot as always!

Great help from you. Easy to understand. Appreciate it a lot!!

Amazing! You are awesome👍

19

Even non-tech people can have legitimate modifications in nsswitch.conf. For example from the avahi/nss-mdnss package. So while this this hint brings the gdm login back, it may easily break other things like .local name lookups.

20

I have three Tumbleweed systems, all with working GDM and a /etc/nsswitch.conf