Public bug reported:

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.

** Affects: systemd (Ubuntu)
     Importance: Medium
         Status: New

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  systemd at 100% handling apport failures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to