Comment 9 for bug 2066995
Revision history for this message
| Simon Chopin (schopin) wrote Re: apport-gtk keeps prompting to report crashes in a loop | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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.