Public bug reported:
I am using the pam-krb5 module to log into a Kerberos realm using
lightdm. This works the initial time I log in, when I come in through
lightdm. However, once I am logged in, and I lock the screen using
light-locker, when I unlock the screen I no longer get renewed tickets.
Launchpad Bug Tracker 1296...@bugs.launchpad.net writes:
So what is happening is that on the initial login, I get a valid ticket
cache, owned by my logging-in user, and showing my UID in the file name.
This ticket works fine. However, once I lock the screen and then unlock
it, I get a ticket
Thank you, Russ, for the insightful explanation of what is happening
here. I can definitely confirm that xscreensaver does indeed work on my
system, as that is what I am using as a workaround to this issue. It
isn't as polished as using the lightdm screen saver would be, but it
certainly works
I took a closer look at the code. It looks like whatever is going on here
is more complicated than just the screen locker not using PAM properly,
although there is one error here:
/* If nothing to run just refresh credentials because we successfully
authenticated */
if (command_argc ==
