04-10-2017, 03:44 AM
As yet I have made no attempt to anticipate when systemd kills plymouth. I can do a fade or something else near the end, but would have to add a tweakable variable to the script so that users could 'tune' the timing to their system. Otherwise it would fade too soon or too late. Every system is different. So for now it just plays until plymouth dies. Without a progress bar, it is only an activity indicator like your recent offering.
If fact, it does have a progress bar (disabled) that could also be 'tuned' to reach 100% just before plymouth dies. I don't mind the tuning. But others will not want to.
If fact, it does have a progress bar (disabled) that could also be 'tuned' to reach 100% just before plymouth dies. I don't mind the tuning. But others will not want to.
(1) LL5.2 on System76 Gazelle Pro L4P9 (2012) i7-3630QM 2.4 GHz - 8GB - Intel HD 4000 1920x1080
(2) LL5.2 on Dell Latitude E5540 (2015) i5-4310U 2.0 GHz - 8GB - Intel HD 4400 1920x1080
(3) Xubuntu 18.04 on 32bit Acer Aspire 5672 (2006) Core Duo T2300 1.66 GHz - 4GB - ATI Mobility Radeon X1400 1280x800
(4) LL4.6 on HP Compaq 8000 SFF (2009) Core 2 Duo E8400 3.0 GHz - 4GB - Intel 4 Integrated Graphics 1920x1080
(5) LL4.6 on Acer Aspire 5515 (2009) AMD Athlon 2650e 1.6 GHz - 3GB - ATI Radeon Xpress 1200 1280x800
(2) LL5.2 on Dell Latitude E5540 (2015) i5-4310U 2.0 GHz - 8GB - Intel HD 4400 1920x1080
(3) Xubuntu 18.04 on 32bit Acer Aspire 5672 (2006) Core Duo T2300 1.66 GHz - 4GB - ATI Mobility Radeon X1400 1280x800
(4) LL4.6 on HP Compaq 8000 SFF (2009) Core 2 Duo E8400 3.0 GHz - 4GB - Intel 4 Integrated Graphics 1920x1080
(5) LL4.6 on Acer Aspire 5515 (2009) AMD Athlon 2650e 1.6 GHz - 3GB - ATI Radeon Xpress 1200 1280x800