[Bug 1895631] Re: systemd at 100% handling apport failures

[Martin Vysny]

This started to happen to me as well after experiencing a hard kernel
crash described at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896446

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1895631

Title:
  systemd at 100% handling apport failures

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd is pegged at 100% after booting Groovy Desktop.

  Seems like an apport-report.service issue:

  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly.

  I removed apport to resolve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895631/+subscriptions