On Sat, Oct 02, 2010 at 03:09:48AM -, Pekka Hämäläinen wrote:
So, before dropping this libpam problem I would recommend that we try to
get the root causes visible. Thus I need some help how to get these logs
generated in first place.
Please file a separate bug report on apt for this.
Unfortunately, without any logs, I don't think there's anything we're
going to be able to do here. Please check that you have sufficient disk
space on /var for logging to happen, and if the problem recurs, please
open a new bug report.
** Changed in: pam (Ubuntu)
Status: Incomplete =
Well, I have bug 560748 open as well. What I can tell is that there
exist plenty of hd space, and I can see the log generated in the console
screen, somehow that is not written to disc. So either the bug above
prevents the log being written or then I gave popped yet an another bug,
this time
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/642591/+attachment/1606787/+files/Dependencies.txt
** Attachment added: VarLogDistupgrade201009190834.gz
https://bugs.launchpad.net/bugs/642591/+attachment/1606788/+files/VarLogDistupgrade201009190834.gz
--
package
Thank you for taking the time to report this issue and help to improve
Ubuntu.
The VarLogDistupgrade201009190834.gz logfile attached to your bug report
is empty. Please attach /var/log/apt/term.log, which might show us
something about how this package's upgrade is failing.
** Changed in: pam
On Sun, 2010-09-19 at 11:09 +, Steve Langasek wrote:
Thank you for taking the time to report this issue and help to improve
Ubuntu.
The VarLogDistupgrade201009190834.gz logfile attached to your bug report
is empty. Please attach /var/log/apt/term.log, which might show us
something
Ok, here is the /var/log/apt/term.log for today
Log started: 2010-09-19 07:41:32
(Reading database ... 141323 files and directories currently installed.)
Preparing to replace linux-image-2.6.24-28-generic 2.6.24-28.77 (using
.../linux-image-2.6.24-28-generic_2.6.24-28.79_amd64.deb) ...
Done.
