We have a nice new graphical boot splash but the text mode one hasn't been updated to match. We've tried to design one here: https://live.gnome.org/GnomeOS/Design/Whiteboards/Boot
Created attachment 67638 [details] [review] Add contact plugin
Created attachment 86406 [details] [review] Add contact plugin Updated to use black background.
Created attachment 86407 [details] [review] Make contact plugin the default text plugin
Created attachment 86408 [details] [review] Make text the default theme
i've pushed attachment 86406 [details] [review] and 86407. Instead of 86408 what about: 1) making spinner start out as system gray with no other content 2) after 5-10 seconds fade up the spinner
I think we want to do black instead of system gray now. Especially since grub is going to use black. That way we'll only do one fade - into GDM. Agreed on IRC to make this plugin start the animation after 5-10 seconds instead of trying to do it daemon side. I think we still want to use this style of progress rather than the spinner.
FWIW, Windows seems to leave the firmware background intact on boot, and use the space underneath the logo to display its animation, so the vendor logo will stay up until the end of boot, reducing transitions.
the bios boot screen is exposed on EFI machines in /sys via BGRT I believe. plymouth doesn't currently use that information. I've commited this change here: http://cgit.freedesktop.org/plymouth/commit/?id=17976ac53807d93d9e240e85fe0e1e8ea3fab730 to the two-step plugin to delay starting the splash for 5 seconds. We do still clear the screen to black, which we might be able to fix, not sure. I'll commit a similar to fix to the text plugin.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/48.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.