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
?
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
apport-gtk fails to report bugs on itself?
https://bugs.launchpad.net/bugs/340742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
