Activity log for bug #340742

Date Who What changed Old value New value Message
2009-03-10 20:31:46 Martin Olsson bug added bug
2009-03-23 18:09:05 Martin Pitt apport (Ubuntu): status New Incomplete
2009-03-25 15:18:46 Martin Olsson apport: status Incomplete New
2009-03-25 15:18:46 Martin Olsson apport: statusexplanation Darn, I saw this bug report too late, and now /var/log/apport.log is gone. Actually apport has a built-in crash counter, so it stops to report crashes of a program after the third time in a day. Apparently this didn't work? Did you get a neverending succession of crash reports? If you encounter this again, can you please attach /var/log/apport.log here? Of course apport could refuse to report crashes of its own, but in 99% of the cases these are actually useful. SIGSEGV are never related to apport itself, but often to python-gtk, or python itself, and thus releavant to other system parts as well. Do you still happen to have the apport-gtk related .crash file? Could you please report it through apport-cli -c /var/crash/_usr_bin_apport-gtk*.crash ?
2009-04-21 10:43:50 Martin Pitt summary apport-gtk fails to report bugs on itself? libapt-pkg-libc6.9-6.so.4.7.0 segfaults in pkgCache::FindPkg ()
2009-04-21 10:44:00 Martin Pitt affects apport (Ubuntu) apt (Ubuntu)
2009-07-19 17:43:54 Ariel Faigon nominated for series Ubuntu Jaunty
2009-09-25 13:43:00 Jonathan Thomas marked as duplicate 119707