[Bug 790538] Re: pam update causes cron to stop working with "Module is unknown" error
Kate Stewart
790538 at bugs.launchpad.net
Tue May 31 16:44:45 UTC 2011
Adding in the set of affected series, for tracking purposes.
** Also affects: pam (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: pam (Ubuntu Hardy)
Status: New => Confirmed
** Changed in: pam (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: pam (Ubuntu Maverick)
Status: New => Confirmed
** Changed in: pam (Ubuntu Natty)
Status: New => Confirmed
** Changed in: pam (Ubuntu Hardy)
Importance: Undecided => Critical
** Changed in: pam (Ubuntu Lucid)
Importance: Undecided => Critical
** Changed in: pam (Ubuntu Maverick)
Importance: Undecided => Critical
** Changed in: pam (Ubuntu Natty)
Importance: Undecided => Critical
--
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:
Confirmed
Status in “pam” source package in Maverick:
Confirmed
Status in “pam” source package in Natty:
Confirmed
Status in “pam” source package in Hardy:
Confirmed
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).
More information about the foundations-bugs
mailing list