[Bug 790538] Re: pam update causes cron to stop working with "Module is unknown" error

[Oliver]

Thanks for the fix. Much appreciated! :)

I noticed it because for some of my machines (I run Ubuntu 10.04, 11.04
and Debian 6) stopped sending logcheck reports. Only had the time to
look into it today, though. It wasn't as critical for me, though some of
the backups that landed on the staging area of the server that shovels
them off-site is now a bit more filled than usual ;)


Thanks again.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/790538

Title:
  pam update causes cron to stop working with "Module is unknown" error

Status in “pam” package in Ubuntu:
  Fix Released
Status in “pam” source package in Lucid:
  Fix Released
Status in “pam” source package in Maverick:
  Fix Released
Status in “pam” source package in Natty:
  Fix Released
Status in “pam” source package in Hardy:
  Fix Released

Bug description:
  Upgrading libpam-modules from 1.1.1-4ubuntu1 to 1.1.1-4ubuntu2.2, cron stopped working, just gives a log message "Module is unknown". This happened during unattended-upgrades this night, so there might be a lot of people who didn't realize that yet.
  Downgrading to 1.1.1-4ubuntu1 fixes this.
  Ubuntu 10.10 amd64, almost vanilla, fresh, minimum install + java (ppa) + postgresql9 (ppa).