Comment 7 for bug 139065

Calling "reload" for kdm is not a complete fix, because kdm does not re-exec itself in response to a reload command; this papers over the problem of kdm unexpectedly restarting during upgrade, but leaves unaddressed the root reason for the restart - that after upgrading the PAM modules, users will no longer be able to log in via kdm until it's restarted.

Suggested patch (merge from Debian unstable) to follow.