Description of problem: After applying updates to FC 18 beta 19 on Tuesday, the first reboot gets the white circle filled it which turns into the blue FC logo and the mouse pointer is a spinning blob. The system stays like that. I can do Ctrl-Alt-F2 to get a login prompt. I then login and do 'startx'. X and GDM come up. I then do Software updates on Thursday morning (Thanksgiving day) and reboot. The same problem still happens. This is a 32-bit OS. On another computer, where I am using the 64-bit beta OS, the same problem happened sometimes. If I let it sit long enough, the initial login screen does come up. In case it matters, I have used BleachBit to remove all but 'en' locale ( which saved me 500 meg of disk space) on both machines.
I assume gdm and its sub processes are "running"? Does it make any difference if you in the text console enters 'systemctl restart gdm' ?
After a few restarts on both the 32-bit and 64-bit systems, GDM comes up and I get the login screen. I briefly see the message: Fast TSC calibration failed on the screen just before I get the login screen. But, sometimes, when I do a shutdown or restart, I get a warning about needing the root password because other users are still logged on. But, there are no other users. I have never had that warning in previous versions of Fedora I do not know how to find out if gdm is running.
After applying all updates this morning (Dec 1) and rebooting, the system hung again with the blue FC logo. Doing Ctrl-Alt-F2 to get a login prompt worked and once logged in, I first did 'startx' which worked. I then logged out of X and tried 'systemctl restart gdm' which worked. That got me a login screen. Doing a restart of Linux then got me the login screen.
What gdm and NetworkManager version are you using? Please edit /etc/gdm/custom.conf and add [debug] Enable=true reboot, and when gdm is hanging log in as root on another VT and create a log and attach it here: journalctl --all > journal.log
gdm: 1:3.6.2-1.fc18 (32-bit) NetMngr: 1:0.9.7.0-8.git20121004 When the main gdm window was hanging, I went to another VT and logged in and did 'su -' to start the log process. But, while doing that, the main gdm window finished and gave me a login screen. So, after a couple of reboots, gdm does come up (but very slowly).
Please verify that your system is fully updated from updates-testing. Which selinux-policy are you using?
Software sources has three items: Fedora 18 - i386 Fedora 18 - i386 - Test Updates Fedora 18 - i386 - Updates Check Now gets: All up to date. How do I find out the selinux-policy?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.