I looked into this a bit. There is a pam module that updates lastlog and wtmp (pam_lastlog(8)), which could be stacked in the lightdm pam config. It doesn't update utmp, however, and utmp is what w(1) and who(1) look at -- see the discussion at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=659957.
I guess as it stands, lightdm needs to write the utmp entry, like login(1), since nothing else does. I also propose to add the pam_lastlog module to lightdm's stack to keep lastlog and wtmp up to date. ** Bug watch added: Debian Bug tracker #659957 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659957 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
