*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a
I found this that removing the file in "/var/crash/", stopped systemd-
journal from filling up. Now systemd process is normal after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895573
I'm getting the same error. Systemd-journal is filling up to over a gig of
useless data. Just reports:
"Sep 18 15:27:51 vmc-TC-885 systemd[1]: Failed to start Process error reports
when automatic reporting is enabled."
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
Forgot the mention that I'm on 20.10, upgraded from 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
systemd[1]: Failed to start Process error reports when automatic
reporting
Masking apport-autoreport.service and apport.service solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
systemd[1]: Failed to start Process error reports when automatic
