On Fri, Sep 18, 2020 at 09:18:25PM -0000, Nicolas Bock wrote:
> After deleting the files *.upload{,ed} I can run
>
> $ sudo /usr/share/apport/whoopsie-upload-all
> /var/crash/_usr_bin_emacs-gtk.1000.crash already has info collected
> Marking /var/crash/_usr_bin_emacs-gtk.1000.crash for whoopsie upload
> All reports processed
>
> And get the two files back. The content of the uploaded file is
>
> $ sudo cat _usr_bin_emacs-gtk.1000.uploaded
> 1c9b8196-f9f4-11ea-b6f1-fa163ee63de6
There is an apport cronjob, /etc/cron.daily/apport, which removes
crashes which are older than a week. If I recall correctly this predates
sending crash reports to the Ubuntu Error Tracker and
whoopsie-upload-all. So it'd make sense to have whoopsie-upload-all
remove the .crash and .upload files after the upload succeeded.
However, this is still something goofy going on with systemd.
On Fri, Sep 18, 2020 at 09:18:25PM -0000, Nicolas Bock wrote: apport/ whoopsie- upload- all _usr_bin_ emacs-gtk. 1000.crash already has info collected _usr_bin_ emacs-gtk. 1000.crash for whoopsie upload emacs-gtk. 1000.uploaded f9f4-11ea- b6f1-fa163ee63d e6
> After deleting the files *.upload{,ed} I can run
>
> $ sudo /usr/share/
> /var/crash/
> Marking /var/crash/
> All reports processed
>
> And get the two files back. The content of the uploaded file is
>
> $ sudo cat _usr_bin_
> 1c9b8196-
There is an apport cronjob, /etc/cron. daily/apport, which removes upload- all. So it'd make sense to have whoopsie-upload-all
crashes which are older than a week. If I recall correctly this predates
sending crash reports to the Ubuntu Error Tracker and
whoopsie-
remove the .crash and .upload files after the upload succeeded.
However, this is still something goofy going on with systemd.
--
Brian Murray