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 Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal Status in apport package in Ubuntu: Confirmed Bug description: apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
