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.
--
Brian Murray
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
