> 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*.
My read of the postinst is that it correctly chmod's /var/crash
regardless of whether it did the creating:
mkdir -p -m 3777 /var/crash
chmod g+s /var/crash
chgrp whoopsie /var/crash
I've confirmed that 'mkdir -p -m' doesn't change the mode of an existing
directory. And /var/crash has been on my system since 2019 when this system
was installed, so it's not new here?
Running `dpkg-reconfigure whoopsie` (i.e., triggering a rerun of the
postinst) is sufficient to fix the directory permissions.
But it must have been something else besides the apport postinst that
dropped the g+s bit.
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
