On Tue, Sep 29, 2020 at 12:38:38PM -0000, Nicolas Bock wrote: > Still failing for me. I see now: > > Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when > automatic reporting is enabled... > Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded. > > Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when > automatic reporting is enabled. > Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Start > request repeated too quickly. > Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Failed > with result 'start-limit-hit'. > Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports > when automatic reporting is enabled. > Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.path: Failed with > result 'unit-start-limit-hit'. > > I have 2 crash files in /var/crash. Note that those two files were in > /var/crash already on boot, I didn't add anything to this directory.
Could you please run 'systemctl status whoopsie' and include the output of the command here? -- 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
