mirror of
https://gitlab.freedesktop.org/plymouth/plymouth.git
synced 2026-05-07 08:28:03 +02:00
read-only mirror of https://gitlab.freedesktop.org/plymouth/plymouth
75fc290c24
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> |
||
|---|---|---|
| docs | ||
| images | ||
| po | ||
| scripts | ||
| src | ||
| systemd-units | ||
| themes | ||
| .gitignore | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
plymouth - graphical boot animation and logger Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. It is designed to work on systems with DRM modesetting drivers. The idea is that early on in the boot process the native mode for the computer is set, plymouth uses that mode, and that mode stays throughout the entire boot process up to and after X starts. Ideally, the goal is to get rid of all flicker during startup. For systems that don't have DRM mode settings drivers, plymouth falls back to text mode (it can also use a legacy /dev/fb interface). In either text or graphics mode, the boot messages are completely occluded. After the root file system is mounted read-write, the messages are dumped to /var/log/boot.log. Also, the user can see the messages at any time during boot up by hitting the escape key. Plymouth isn't really designed to be built from source by end users. For it to work correctly, it needs integration with the distribution. Because it starts so early, it needs to be packed into the distribution's initial ram disk, and the distribution needs to poke plymouth to tell it how boot is progressing. plymouth ships with two binaries: /sbin/plymouthd and /bin/plymouth The first one, plymouthd, does all the heavy lifting. It logs the session and shows the splash screen. The second one, /bin/plymouth, is the control interface to plymouthd. It supports things like plymouth show-splash, or plymouth ask-for-password, which trigger the associated action in plymouthd. Plymouth supports various "splash" themes which are analogous to screensavers, but happen at boot time. There are several sample themes shipped with plymouth, but most distributions that use plymouth ship something customized for their distribution. Plymouth isn't done yet. It's still under active development, but is used in several popular distros already, including Fedora, Mandriva, Ubuntu and others. See the distributions page for more information. As with other projects hosted on freedesktop.org, Plymouth follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: https://www.freedesktop.org/wiki/CodeOfConduct