[Bug 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
vmc
1895573 at bugs.launchpad.net
Fri Sep 18 22:45:19 UTC 2020
I found this that removing the file in "/var/crash/", stopped systemd-
journal from filling up. Now systemd process is normal after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
systemd[1]: Failed to start Process error reports when automatic
reporting is enabled.
Status in apport package in Ubuntu:
Confirmed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+subscriptions
More information about the foundations-bugs
mailing list