Red Hat Bugzilla – Bug 470468
Plymouth keeps running if X fails to start
Last modified: 2009-12-18 01:46:26 EST
Description of problem:
When I have some errors in xorg.conf because of which the X won't start, the plymouth won't shut down (nor even notifies the user) and just keeps running forever with progressbar at 100% and active animations.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make some mess in xorg.conf so the X won't start
2. Restart computer with plymouth enabled (vga=... kernel param)
Plymouth just keeps running forever, progressbar stops at 100%, animations are animating and nothing else is happening
Somehow notify the user, that the X failed to start, either show him the X log, or switch to console login or anything else...
I'm using Fedora 10 Preview
I've made a small mistake in the problem description, actually the animations do not go on forever, they stop when the progress bar reaches its end.
plymouth quits before X tries to start. If plymouth is still animating then it means upstart never tried to start X.
I'm thinking you're two problems are related, so I'm going to dupe this one to the other one.
*** This bug has been marked as a duplicate of bug 470471 ***
reopening because of bug 470471 comment 11
I think I have the same or a related bug. I'm running a dual-core dell pentium D with an ATI video card (R300 I believe). I used the netinstall disk to upgrade a working F9 install to F10 preview. Plymouth works AOK out of the box, but stalls at 100% progressbar. The animations stop and the system is hung. If I pass 'nomodeset', it drops into X with gdm. However, rendering of text is messed up once in. Portions of text in a variety of applications (terminal, web browser, etc.) just disappear. I assumed that this was because of a problem with the way the graphics card is being initialized, but I realized it could be something else too.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Not sure if this is related, but noted this behavior with today's kernel update.
I have an nVidia GPU and I use the nVidia installer, rather than the Livna/RPMFusion RPMs.
Typically, when booting to a new kernel, X will of course fail, until the nVidia driver is installed.
In such a case, the graphical boot process would "gracefully" fail and leave me at a text mode console, where I could login as root, re-install the nVidia driver and then run 'init 5' to get back into X.
After today's kernel update, Plymouth seems to just leave me at a black screen after X fails to start. I can type letters at the screen, but to no avail. There is no login prompt, etc.
If this behavior is not related, let me know and I will file a separate bug.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
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 prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.
Thank you for reporting this bug and we are sorry it could not be fixed.