Do you know what I can do about the cleanup?
Thanks
On Sun, Nov 29, 2009 at 1:26 PM, Jean-Baptiste Lallement <
jeanbaptiste.lallem...@gmail.com> wrote:
> Thanks for following up. This is likely a duplicate of bug 238755. The
> later has been fixed in shadow package a while ago but it appears tha
Thanks for following up. This is likely a duplicate of bug 238755. The
later has been fixed in shadow package a while ago but it appears that
debian/patches/494_passwd_lock-no_account_lock has been applied upstream
in 4.1.3 and hence dropped from Debian/Ubuntu.
Another report with the same use cas
I manually reinstalled kerneloops-daemon (plus a couple of others that had
the same problem - speech-dispatcher and couchdb).
I didn't know that root needs to be unlocked to update!
In addition, postgreSQL did not upgrade from 8.3 -> 8.4.
Because of these errors, the update-manager did not clean
Thanks for your report.
The error is
Setting up kerneloops-daemon (0.12+git20090217-1ubuntu4.1) ...
Your account has expired; please contact your system administrator
chfn: PAM authentication failed
adduser: `/usr/bin/chfn -f Kernel Oops Tracking Daemon kernoops' returned error
code 1. Exiting.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36220746/Dependencies.txt
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/36220747/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibra
