Apport keeps reshooting apport-autoreport.service as long as there are files like /var/crash/*.crash:
# cat /lib/systemd/system/apport-autoreport.path [Unit] Description=Process error reports when automatic reporting is enabled (file watch) ConditionPathExists=/var/lib/apport/autoreport [Path] PathExistsGlob=/var/crash/*.crash [Install] WantedBy=paths.target # cat /lib/systemd/system/apport-autoreport.service [Unit] Description=Process error reports when automatic reporting is enabled ConditionPathExists=/var/lib/apport/autoreport Wants=whoopsie.service After=whoopsie.service [Service] Type=oneshot ExecStart=/usr/share/apport/whoopsie-upload-all If the service succeeds there is no reason for systemd to not restart it. IMO apport should check the files once after the boot finised and monitor /var/crash/ for _changes_ only while the system is running. I still check if something could be done on systemd side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
