I have this issue too. It causes systemd's PID 1 (`/sbin/init splash` in htop) to use 100% CPU, which seems unfortunate.
When it happens, the log is filled with a whole lot of lines like this: Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Followed by logs like this: Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: All reports processed Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: All reports processed Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: All reports processed Sep 11 10:00:03 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:03 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:03 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
