Ah, I think this can happen on a multi-user system where .crash files owned by a user other than the logged in user exist. In asala's /var/crash directory we can see .crash files owned by asala and by user.
We can get the same permission denied error by running the following on a crash file we don't own:
Ah, I think this can happen on a multi-user system where .crash files owned by a user other than the logged in user exist. In asala's /var/crash directory we can see .crash files owned by asala and by user.
We can get the same permission denied error by running the following on a crash file we don't own:
/usr/share/ apport/ apport- gtk /var/crash/ _usr_bin_ compiz. 1000.crash
However, running /usr/share/ apport/ apport- checkreports does not return 0 indicating that there is a new crash for us....