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

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.2-2ubuntu8.3

---------------
pam (1.1.2-2ubuntu8.3) natty-security; urgency=low

  * SECURITY REGRESSION:
    - debian/patches/security-dropprivs.patch: updated patch to preserve
      ABI and prevent daemons from needing to be restarted. (LP: #790538)
    - debian/patches/autoconf.patch: refreshed
 -- Marc Deslauriers <marc.deslauriers at ubuntu.com>   Tue, 31 May 2011 05:48:25 -0400

** Changed in: pam (Ubuntu Natty)
       Status: Confirmed => Fix Released

** Changed in: pam (Ubuntu Maverick)
       Status: Confirmed => Fix Released

-- 
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:
  Confirmed
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).