Here is the debdiff that fixes this bug. Packages with this patch should be built soon at https://launchpad.net/~urusha/+archive/bug952771
** Patch added: "precise debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/952771/+attachment/3446688/+files/gnome-screensaver-precise.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/952771 Title: Gnome Screensaver should handle expired password tokens Status in GNOME Screensaver: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Gnome Screensaver should handle expired password tokens. Currently it does not. It just unlocks screen, so in case you're using kerberos - your credentials cache stays expired and you need to manually change your password or logout and then login again (lightdm, gdm, etc. do handle expired password tokens). Actually, there is a mainstream bugreport with patch solving the problem, but it seems noone is interested in solving this issue: https://bugzilla.gnome.org/show_bug.cgi?id=648875 The patch provided by Brian C. Huffman solves the issue and is compatible with today's GS behavior (it can be emulated using special pam config, see comment 9 there). Both solutions using this patch (with and without "passwd required pam_permit.so") tested by me with oneiric's gnome-screensaver-3.2.0-ubuntu1 and work as expected. This is really nice improvement for big corporate environments. So, It would be nice to apply this patch even if it's not in upstream yet. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/952771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp