Comment 3 for bug 985735

So bug #744944 dealt with this same issue with pam, where it was concluded that kdm does not need to be restarted on libpam upgrade because libpam is not loaded persistently so will always get the new version of the library no matter what.

I'm not sure the same can be said for libc. If kdm only does all its username lookups in a short-lived helper process of the daemon, then it's probably ok to have eglibc not restart it. Otherwise, we're just trading one failure scenario for another here - either kdm gets ungracefully restarted out from under the desktop mid-upgrade, or kdm is left running but is no longer able to let users back in if the user logs out for some reason.

Some guidance from the kubuntu developers is needed here about what we should do. Is there a different method we should use to request a graceful restart of kdm? Should we just leave kdm running for the current session, knowing users may be locked out afterwards due to NSS mismatches?