Public bug reported:
This occurred on a machine that has been dist-upgraded from
breezy to etch and all the points in between, with official sources.
If apport is installed, the /etc/cron.daily/apport script tries to run
a find over /var/crash and that directory may not actually be there.
This generates irritating emails to root.
If the other bits of apport create /var/crash at the time of the first
crash after installation, then perhaps the cron.daily needs this patch:
--- apport.old 2006-10-10 00:49:47.000000000 +1000
+++ apport 2006-11-13 15:50:17.000000000 +1100
@@ -1,4 +1,5 @@
#!/bin/sh -e
# clean all crash reports which are older than a week.
+[ -d /var/crash ] || exit 0
find /var/crash -mindepth 1 -mtime +7 -print0 | xargs -0 rm -f
find /var/crash -mindepth 1 -empty -print0 | xargs -0 rm -f
dpkg -l python-problem-report python-apport-utils apport
ii apport 0.28 automatically generate crash reports for deb
ii python-apport- 0.28 apport crash report handling functions
ii python-problem 0.28 python library to handle problem reports
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
doesn't create /var/crash (?)
https://launchpad.net/bugs/71599
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
