Hide Forgot
We are working on parallelizing as much as we can during boot. That means among other things that probing of hardware devices (udev trigger and its effects) can be done in parallel with other bootup tasks and that those other tasks listen actively on hardware showing up instead of expecting to be started only after all hardware has been probed. Hardware probing is a relatively slow operation, on my laptop for example it usually takes 8s or so to be fully complete, due to my 3G modem not reacting any faster if it has no SIM card. On-initrd-less systems this currently creates a problem with Plymouth: since we start Plymouth before udev is finished probing it will not find any framebuffer devices and alway show the text animations. This is not a problem in the initrd otoh since 3G is not probed there. So yeah, I think Plymouth really needs to listen actively for devices popping up with libudev, and make use of them as they show up. Otherwise a working plmyouth means that we have to settle device probing before starting it, which means the plymouth screen is shown very late and we need to delay the bootup just for it.
Actually, on boots with dracut this behaviour of Plymouth costs me around 3s boot time, since we need to wait until all graphics cards are probed before we can start Plymouth, and that is really slow, > 2s here, and means that the initrd is really slow. Also see the footnotes of: http://0pointer.de/blog/projects/blame-game.html
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.