Red Hat Bugzilla – Bug 799686
Plymouth boot splash is randomly interrupted
Last modified: 2012-03-07 01:36:13 EST
Description of problem:
The boot splash rendered by Plymouth is sometimes interrupted and either a text-mode boot screen flashes and disrupts the continuity of the splash, or the splash disappears for several seconds or till the completion of the boot process and the text mode is displayed instead, without any boot messages in both cases. I have noticed that when this does happen, it always does so when the system attempts to start the Plymouth service. What I cannot understand is, since the message about starting the Plymouth service appears quite late in the boot sequence (the service is apparently started after several others), how and/or why is the splash screen shown before that anyway? Also, I could not figure out whether this problem is caused by Plymouth or systemd, so I have not been able to select the proper component for this bug report.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a Fedora desktop system with Plymouth enabled.
The splash screen is sometimes interrupted by display of the text mode.
The splash screen is displayed continuously in an uninterrupted manner during the entire boot process.
I have installed my system, on which this happens, from a live image on a Dell Inspiron 1545 laptop with integrated Intel GM45 graphics.
This is almost certainly "interactions between plymouth and systemd".
Moving to systemd, cc'ing plymouth maintainer.
More likely this is an xorg-x11-drv-intel bug which affects all 3.kernels .
We have had quite a few of those lately which are having weird effects like monitors suddenly suspend when plymouth loads and what not.
The easiest way to test if that's the case is to install and boot pre 3.x kernel or follow what's something like is suggested in comment 8 and comment 9 in bug 753881
Or it could be bug 785662
Yes, it does seem to be bug 785662. I'll close this one as a duplicate after some more testing. Thanks.
*** This bug has been marked as a duplicate of bug 785662 ***