I see you also pulled in the libc and pam updates. During the libc upgrade there should have been a dialog requesting service restarts for ssh and cupsd as the upgrade breaks authentication. The wall of text explaining the upgrade should have stated that X (and therefore kdm) needs to be restarted manually after the upgrade, as restarting X logs out any active sessions and would therefore kill the upgrade. ssh works because it can be restarted safely.
This happens every time libc and pam are updated and is due to a limitation in pam. TLDR; Any time you upgrade libc or pam, you /must/ log out and restart kdm. /not maintainer -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130920015451.3...@web006.roc2.bluetie.com
