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

Paul Boven p.boven at xs4all.nl
Tue May 31 16:53:02 UTC 2011


Just for the record: pulling the pam packages like this completely
breaks the network-based install I'm doing from an official Ubuntu
mirror, because of the 404-errors.

-- 
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