Ubuntu
apport package

systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

Bug #1895573 reported by Mert Can Demir
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

htop always shows 100% CPU for /sbin/init/splash

When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing.

Revision history for this message
Mert Can Demir (validatedev) wrote :
Revision history for this message
Mert Can Demir (validatedev) wrote :

Masking apport-autoreport.service and apport.service solves the issue.

Revision history for this message
Mert Can Demir (validatedev) wrote :

Forgot the mention that I'm on 20.10, upgraded from 20.04.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
vmc (vmclark) wrote :

I'm getting the same error. Systemd-journal is filling up to over a gig of useless data. Just reports:
"Sep 18 15:27:51 vmc-TC-885 systemd[1]: Failed to start Process error reports when automatic reporting is enabled."

Revision history for this message
vmc (vmclark) wrote :

I found this that removing the file in "/var/crash/", stopped systemd-journal from filling up. Now systemd process is normal after a reboot.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.