Still failing for me. I see now:
Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.path: Failed with result 'unit-start-limit-hit'.
I have 2 crash files in /var/crash. Note that those two files were in /var/crash already on boot, I didn't add anything to this directory.
Still failing for me. I see now:
Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... autoreport. service: Succeeded. autoreport. service: Start request repeated too quickly. autoreport. service: Failed with result 'start-limit-hit'. autoreport. path: Failed with result 'unit-start- limit-hit' .
Sep 29 06:32:27 rubberducky systemd[1]: apport-
Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 29 06:32:27 rubberducky systemd[1]: apport-
Sep 29 06:32:27 rubberducky systemd[1]: apport-
Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Sep 29 06:32:27 rubberducky systemd[1]: apport-
I have 2 crash files in /var/crash. Note that those two files were in /var/crash already on boot, I didn't add anything to this directory.