All plymouth's systemd unit files are meant to only run once, either during boot or during shutdown/restart. Certain events cause systemd to recheck the dependency try between systemd units. Systemd had a bug before the 245 release which caused this check to sometimes not restart exited services for which the dependencies are met. Systemd 245 fixes this, this is causing problems with plymouth. When the conditions are met for systemd to recheck the dependencies; and the plymouthd started by plymouth-start.service has exited; then systemd will restart the plymouth-start unit, causing plymouthd to take over tty1 after boot. This is causing various problems, also see: https://bugzilla.redhat.com/show_bug.cgi?id=1803293 Since all plymouth's systemd units are intended to run only once, they all should be marked as remaining after exit by adding: "RemainAfterExit=yes" to them. This causes systemd to still consider them running after e.g. plymouthd has exited, as long as they have started successfully. This fixes systemd restarting plymouth's units when it should not do so. BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1803293 BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1807771 Signed-off-by: Hans de Goede <hdegoede@redhat.com>calculate-0.9.5
parent
ba8483fc2c
commit
75fc290c24
Loading…
Reference in new issue