So if the command prompt only shows up briefly, that plymouth-stop has been triggered by the init scripts ('rc') finishing before gdm is ready to start.
This may indeed be affected by ureadahead, but it wouldn't be a ureadahead bug. We just are not defined to have gdm start before the init scripts have finished, so sometimes there may be a gap.
Reassigning to plymouth; I'm not sure what we can do about it in practice, but that's the package responsible for the boot splash.
So if the command prompt only shows up briefly, that plymouth-stop has been triggered by the init scripts ('rc') finishing before gdm is ready to start.
This may indeed be affected by ureadahead, but it wouldn't be a ureadahead bug. We just are not defined to have gdm start before the init scripts have finished, so sometimes there may be a gap.
Reassigning to plymouth; I'm not sure what we can do about it in practice, but that's the package responsible for the boot splash.