Even in systemd this is is going to be trickier than I though if we want to do the things right since sadly dh-nss has some issues: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1113745
And in particular, it does not allow us to ensure that the service is set for all the databases, given that it considers "good enough" a nsswitch.conf that contains the systemd service in at least one database (sadly the grep command it generates and that I pasted above, would just pass in a broken nss switch, since multiple grep patterns are not in AND form). So... I initially thought that forcing a preinst script to re-generate the nsswitch (as in https://code.launchpad.net/~3v1n0/ubuntu/+source/systemd/+git/systemd/+merge/491734) would have been enough to fix our problems, but as said the script wouldn't run... Thus various possibilities: 1. Fix dh-nss as in the upstream bug (will it happen in time?) 2. Workaround the problem by dropping all the systemd instances in the /etc/nsswitch preinst and then make dh-nss to fix it in postinst 2a. I said dropping all the systemd instances for a reason: if we don't do it, we'll end up with duplicates ** Bug watch added: Debian Bug tracker #1113745 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1113745 ** Also affects: dh-nss (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1113745 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2121017 Title: gdm3 49~beta doesn't start [unix_chkpwd: could not obtain user info (gdm-greeter)] on systems installed before 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-nss/+bug/2121017/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
