"Again, the question is what else needs to be restarted?" The answer to that is "I don't know", which is why the general recommendation here should be to just reboot. Basically, any long- running process with the older libc loaded that tries to do NSS DNS lookups will fail. This was the bug introduced in the previous update, and reverted in this, but of course, the revert will have the same effect as the original update if you upgraded and restarted with the interim libc.
Again, this sucks, but there's no sane way to both revert the ABI break and make it smooth for the people who restarted services (or the machine) with the bad update in between. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: glibc update caused NSS ABI break To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
