I found the wild goose! Your Python crashes are owned by vorlon:vorlon, which is why whoopsie cannot read them. I'm guessing that /var/crash doesn't have the 3777 permissions that would allow inheriting the whoopsie GID. My own system has 1777, whereas fresh containers seem to be correctly using 3777.
It seems to boil down to a race condition between the apport postinst and the whoopsie postinst, the latter correctly chmoding /var/crash to 3777 *if it creates it*. We should fix the apport postinst to use the proper permissions and fix existing installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
