Red Hat Bugzilla – Bug 679503
plymouth doesn't always transition to gdm
Last modified: 2013-09-02 02:55:04 EDT
Created attachment 480197 [details]
Description of problem:
Every 4 or 5 boot ups, plymouth fails to transition to the graphical login (gdm).
Version-Release number of selected component (if applicable):
1 of every 4 or 5 system boots
Steps to Reproduce:
1. Boot a system
2. Enter passphrase for encrypted '/' and swap partitions
Plymouth continues to show graphical boot progress, and doesn't transition to gdm. I can chvt and login on different tty's
Graphical display manager (gdm)
* See attached plymouth:debug log
* When plymouth got stuck, I logged in via tty2 and killed plymouthd
# pkill -SEGV -f plymouthd
*** Bug 682327 has been marked as a duplicate of this bug. ***
I was seeing this consistently on live images I was building for the GNOME 3 Test Day; on my test laptop gdm would never start, the live image just booted to a console and systemd said prefdm.service start was 'waiting'.
I had to add rd_NO_PLYMOUTH to the live image boot parameters to avoid this.
Discussed at 2011-03-11 blocker review meeting. We'd like a little more data to be sure of the impact of this one; I was testing only on one system so if this is timing dependent it may not hit other systems. This issue should be present on current nightlies (as they don't have the workaround of disabling Plymouth), so feedback from people testing the nightlies would be useful.
I haven't observed this issue for a fully updated F15 anymore for a few days now.
(In reply to comment #4)
> I haven't observed this issue for a fully updated F15 anymore for a few days
Likewise, I've not seen this problem in a long time on my existing F-15 install.
Discussed at 2011-03-18 blocker review meeting. This was proposed due to issues I was seeing with the test day live images, but we decided to close this as neither reporter is seeing the initial issue any more. I will file a new bug if latest nightlies still have problems on my test system.