When will GDM bug 1250513 get fixed?

English Install/Boot/Login
1

I’m a tech noob.

This GDM bug 1250513 – [Build 20250924] Upgrades from 15.x seem to get the config for gdm / dynamic user generation wrong is marked as “Severity: Major”. So I’m assuming it’ll get fixed quickly, maybe in a few days. That sound right? Or could it take a lot longer to get fixed?

If it’ll take longer, I’ll invest some time to explore the nsswitch fix.

(Also see Comment 20 on the Bugzilla page for this bug. The commenter there essentially has the same question as I do.)

I’m using an older snapshot and not running any zypper dup.

Right now the bug is still on Confirmed and I’m checking it once or twice a day.

(A few days ago this bug stopped me from getting to the login screen, and I had to rollback to an older snapshot.)

1 Like
2

It needs 10 seconds to apply the fix to your config.
If you read the bugreport, you will find that there won’t be an automated solution (via update) soon.

There are several threads in the forum which explains how to do it. Simply perform the update of your machine via zypper dup. Afterwards move/rename/(delete) /etc/nsswitch.conf. Or if you want, edit the content.

1 Like
3

OK, good to know.

4

I explore that link.

If I fix the nsswitch thing, will the same problem return when I do another sudo zypper dup and reboot?

Also, is there any way to tell if my nsswitch has been modified? Just want to do some research in case moving my nsswitch causes some other issues.

If the root bug will not be fixed for a long time, it seems I’ll have to apply this nsswitch fix every time I run sudo zypper dup.

5

If there is a fix for this bug, it will probably involve changing “nsswitch.conf”. But, to do that with a bug fix they will need to come up with a change that can apply to everyone. That’s actually complicated.

Your best bet is to simply fix “nsswitch” on your own system.

1 Like
6

@invalid_user_name if your using zeroconf, then just install nss-mdns and be done or delete the file, it won’t get changed in /etc as that’s for system admins to use.

1 Like
7

Hmmm… I’ve never heard of of “zeroconf” or “nss-mdns” and have no idea what they are, or what they do, or how to use them.

But no problem, I’ll start doing some googling and AI searches to learn.

If you or someone else could give me a few hints or pointers about using “zeroconf” and nss-mdns to solve the issue, this tech noob would appreciate it.

And I know this is the world of Linux, sometimes I have no choice but to bite the bullet and teach myself some gnarly tech.

8

@invalid_user_name zypper if nss-mdns and check the description. I use for my HP Printer… have not been affected by this bug either?

1 Like
9

I don’t understand this question. Could you explain? Are you asking if I’ve not been affected by this bug?

10

Thanks all for the info. as I have been holding off updating the machine I use daily. I have had a look at my nssswitch.conf file and it just seem to be an example file with instructions on how to configure it. I updated a couple of other less used / crucial machines & they updated without problems. I did use the Gnome Software updater and did those updates off line on a reboot FWIW if that makes any difference?

Any way question is if I don’t seem to have anything in the nss file then am likely to be unaffected by this? I’m using Tumbleweed with Wayland as were the other 2 machines so I’m hoping so.

1 Like
11

I was affected and deleted the file.
I updated again yesterday and everything still works.

12

@invalid_user_name No, I meant that I’ve not see the GDM bug that you and others are seeing… :wink:

1 Like
13

@invalid_user_name as an aside you may be interested in this for using that package :wink:

14

Sorry to hear that but glad it worked out for you. I plucked up the courage to try the update with quite a few gigabytes to do as I had been holding off. The gnome software route failed because to add to the peril there was a Nvidia update too! So reverted to dup & accepting those licences & fortunately it rebooted OK for me. SO maybe if you have nothing in the nssswitch.conf file then you’ll be fine? The only annoyance I had was as others have observed in another thread was in relation to the upgrade of Evolution. This meant I had to re authorise my outlook e-mail in the online accounts, which proved a bit troublesome, but I got there in the end. hurrah & a happy weekend to all.

1 Like
15

I hired a remote access Linux expert and he checked and showed me that moving nsswitch should not cause any issues. We applied the mitigation and it’s working now. I’m now able to successfully run zypper dup without getting a black screen.

16

Just be aware, if you did connect to network devices using mDNS (like you’re using GNOME network browser or a printer using a .local address), you’ll probably need nsswitch.conf. In that case, restore the file and add “systemd” to passwd, group and shadow lines.

1 Like
17

Never heard of that stuff, have no idea what it means. So that means…time for me to google and learn!

18

My printer is connected via USB cable. I tested it and it’s printing fine. So I guess I’m all set there.

19

The only “networking” I do is connecting to the internet thru my 5G wifi hotspot. No ethernet or anything like that.

20

Below is me copy/pasting some commands provided by google.

advait@localhost:~> sudo systemctl status avahi-daemon.service
[sudo] password for root: 
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-10-09 07:16:27 IST; 6h ago
 Invocation: 55db90442a734ea6a0e6067c7be6843c
TriggeredBy: ● avahi-daemon.socket
   Main PID: 1468 (avahi-daemon)
     Status: "Server startup complete. Host name is linux.local. Local service cookie is 2797470648."
      Tasks: 1 (limit: 47203)
        CPU: 214ms
     CGroup: /system.slice/avahi-daemon.service
             └─1468 "avahi-daemon: running [linux.local]"

Oct 09 10:03:53 localhost.localdomain avahi-daemon[1468]: Interface wlp4s0.IPv4 no longer relevant for mDNS.
Oct 09 10:03:53 localhost.localdomain avahi-daemon[1468]: Files changed, reloading.
Oct 09 10:03:53 localhost.localdomain avahi-daemon[1468]: No service file found in /etc/avahi/services.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: Files changed, reloading.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: No service file found in /etc/avahi/services.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: Joining mDNS multicast group on interface wlp4s0.IPv4 with address 172.30.216.24.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: New relevant interface wlp4s0.IPv4 for mDNS.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: Registering new address record for 172.30.216.24 on wlp4s0.IPv4.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: Files changed, reloading.
Oct 09 12:57:06 localhost.localdomain avahi-daemon[1468]: No service file found in /etc/avahi/services.

advait@localhost:~>     ping linux.local
ping: linux.local: Name or service not known

advait@localhost:~> ping linux.local
ping: linux.local: Name or service not known

advait@localhost:~> hostname --fqdn
localhost

advait@localhost:~> ping localhost.local
ping: localhost.local: Name or service not known

advait@localhost:~> ping localhost
PING localhost (::1) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.054 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.131 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.123 ms
64 bytes from localhost (::1): icmp_seq=4 ttl=64 time=0.064 ms
64 bytes from localhost (::1): icmp_seq=5 ttl=64 time=0.076 ms
^C
--- localhost ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4085ms
rtt min/avg/max/mdev = 0.054/0.089/0.131/0.031 ms

advait@localhost:~> hostname --long
localhost

advait@localhost:~> avahi-resolve -n "$localhost.local"

The program 'avahi-resolve' can be found in the following package:
  * avahi-utils [ path: /usr/bin/avahi-resolve, repository: download.opensuse.org-oss ]

Try installing with:
    sudo zypper install avahi-utils

advait@localhost:~> avahi-resolve -n "$localhost"

The program 'avahi-resolve' can be found in the following package:
  * avahi-utils [ path: /usr/bin/avahi-resolve, repository: download.opensuse.org-oss ]

Try installing with:
    sudo zypper install avahi-utils

advait@localhost:~> avahi-resolve -n $localhost

The program 'avahi-resolve' can be found in the following package:
  * avahi-utils [ path: /usr/bin/avahi-resolve, repository: download.opensuse.org-oss ]

Try installing with:
    sudo zypper install avahi-utils

advait@localhost:~> avahi-resolve -n $localhost.local

The program 'avahi-resolve' can be found in the following package:
  * avahi-utils [ path: /usr/bin/avahi-resolve, repository: download.opensuse.org-oss ]

Try installing with:
    sudo zypper install avahi-utils

advait@localhost:~> avahi-utils [ path: /usr/bin/avahi-resolve, repository: download.opensuse.org-oss ]
 avahi-utils: command not found

advait@localhost:~> cat /etc/nsswitch.conf | grep hosts
cat: /etc/nsswitch.conf: No such file or directory

advait@localhost:~> cd etc/
bash: cd: etc/: No such file or directory

advait@localhost:~> cd /etc/
advait@localhost:/etc> cat /etc/nsswitch.conf | grep hosts
cat: /etc/nsswitch.conf: No such file or directory

advait@localhost:/etc> Now remembering that the tech support guy I hired "moved" the nsswitch file.