Hide Forgot
Description of problem: After updates, boot hangs, screen enter in stand by mode and I can't use the system. System starts correctly only If I press Esc key on boot sequence. With "nomodeset" option, system seems to start but when it load mouse pointer it freezes again. Version-Release number of selected component (if applicable): plymouth.x86_64 0.8.4-0.20110510.2.fc15 xorg-x11-drv-ati.x86_64 6.14.1-1.20110504gita6d2dba6.fc15 xorg-x11-server-Xorg.x86_64 1.10.1-14.fc15 How reproducible: Steps to Reproduce: 1. Install Fedora 15 Desktop x86_64. 2. Run updates. 3. Reboot system. Actual results: System freezed after reboot, screen in stand-by mode. Expected results: Normal start. Additional info:
With kernel 2.6.39-1 from rawhide, I haven't any boot problem.
Same problem here with a F15 x86/Intel graphics machine. plymouth: 0.8.4-0.20110510.2.fc15 xorg-x11-drv-intel: 2.15.0-3.fc15 xorg-x11-server-Xorg: 1.10.2-1.fc15 kernel: 2.6.38.7-30.fc15.i686
Boot hangs after message Starting wait for Plymouth to quit. Putting /bin/true instead of plymouth --wait in systemd config for plymouth-quit-wait.service does not change anything, so I suspect the problem not in plymouth but in kernel. With older kernel system boots fine. Plymouth is not starting actually because I use proprietary nvidia drivers. And anyway systemd should exit after timout but it does not. Problematic kernel: kernel-2.6.38.7-30.fc15.x86_64 Last working kernel: kernel-2.6.38.6-27.fc15.x86_64 systemd version: systemd-26-2.fc15.x86_64 My guess is: something wrong with kernel-systemd pair.
Can you check the following: 1) What plymouth theme are you using? Does this occur when a different theme is set (try 'text' or 'charge')? 2) Are you able to switch to and use another TTY (Ctrl+Alt+F[2-6])? 3) Let the problem occur, then kill the X-server (ctrl+alt+backspace) and restart w/ ctrl-alt-del. In the flashing systemd shutdown message, do you see a red failure message for plymouth?
I have also encountered what appears to be the same problem. Installed and loaded Fedora 15 (x64) from cd. Run updates. Install skype. install google chrome. change theme. Start of problem. On reading this post and question from 'Ved Vyas' I re-installed (couldn't figure out a way to cure it). Updated. Re-installed software. Made minor tweaks to pre-existing themes and now there is no problem. I can't be certain which theme was the cause of the problem (because I lost the settings on re-install), but they were official themes from the repository. Hope that helps.
I previously encountered this problem with the 'spinfinity' theme. I then discovered that 'charge' and 'solar' worked just fine and stuck with solar. This is with the nvidia blob on F15 x86_64 (vga kernel param is used). When I get a chance, I will confirm that that this is still the case for me, and try running with nouveau. (In reply to comment #5) > Updated. Re-installed software. Made minor tweaks > to pre-existing themes and now there is no problem. > > I can't be certain which theme was the cause of the problem (because I lost the > settings on re-install), but they were official themes from the repository. Greg, which theme are you currently using? Were the minor tweaks to the plymouth theme files, or just the desktop theme? Thanks.
Same problem here with a F15 x86/Intel graphics machine. But I also get the below error. '/sbin/modprobe' unexpected exit with status 0x0009
We have a lab of 50 machines with: Display controller: ATI Technologies Inc RV516 [Radeon X1300 Pro] kernel: 2.6.40.4-5.fc15.x86_64 xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64 plymouth-0.8.4-0.20110510.2.fc15.x86_64 xorg-x11-server-Xorg-1.10.4-1.fc15.x86_64 When these machines are all powered on, about 5-10% will hang early during the boot process at about the time the graphics modeswitch is supposed to happen. These machines are then completely unresponsive: monitor is asleep, network interface is not active, and keyboard is unresponsive (no Caps Lock light; no VT switch; no magic-sysreq). The only remedy is the power button.
*** Bug 754084 has been marked as a duplicate of this bug. ***
On F17 I don't have this issue. Only F15 and F16 seems to be affected by the bug.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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