Description of problem: Previous versions of Fecora (at least until 9) switched from the graphics (X client) screen to tty1 during bootup and shutdown or mirrored those messages to the graphics screen. That was a nice feedback and in particular useful in the following case: In case of a necessary fsck(1) (e.g. after hard reset), the graphics logo (light blue circle with "nose", being filled diagonally with white) seems to be stuck almost at the end of the process, whereas the fsck progress bar is displayed on tty1. This fsck can take several minutes, and there is a significant risk that the unadvertent user considers the system "stuck", makes another hard reset and runs into an infinite loop of reboots. At least it is very annoying to see the system take several minutes for a bootup that usually takes not more than two minutes, without knowing the reason. Version-Release number of selected component (if applicable): initscripts-9.02.1-1.i686 Linux mar** 2.6.31.12-174.2.3.fc12.i686.PAE #1 SMP Mon Jan 18 20:06:44 UTC 2010 i686 i686 i386 GNU/Linux How reproducible: Every reboot/bootup Steps to Reproduce: 1.reboot Actual results: Messages hidden behind graphical screen without significance. Expected results: Show initrd messages during bootup (and also during shutdown) process Additional info:
If you remove both "quiet" and "rhgb" arguments from grub ( /boot/grub/menu.lst ), you'll be able to see any messages shown, previously appearing behind plymouth, anyway some change like this ( timeout before show startup messages ) is a plymouth change Thanks for your report, I'll re-assign it for plymouth team -- Fedora Bugzappers Team Member
Yes, you are right: A timeout for the graphical screen ("plymouth", right?) hiding the initrd messages is probably a good thing. Even better would be that it can disappear immediately, in case of an unusual event, like rc script failed or fsck triggered.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.
This bug is still present in fc13, probably also fc14, as no feedback had been given from plymouth debuggers.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Yes, sorry. I forgot to confirm that the situation in F14 is unchanged. This request for improvement is still valid. The "fsck" step is probably the longest single step during bootup, as it can take minutes in the extreme case. If a general solution cannot be found to interface the messages to plymoth (as before F10?), then it might be worth thinking about a special implementation of a "progress bar" for the "fsck" step, in order to give users an indication that the boot is not stuck.
There are plans to add better fsck support to plymouth and systemd
(In reply to comment #8) > There are plans to add better fsck support to plymouth and systemd Hello, That is nice to hear. Can I expect it to be available for F15?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping