This one's pretty easy to reproduce: on a Fedora 22 or Rawhide system with gdm, enable autologin, then boot a few times.
You can also reproduce it just by booting any recent 22 Workstation live image a few times.
As long as 'rhgb quiet' are on the cmdline, sometimes the system will get stuck at the point when gdm should kick in and bring up the desktop, with the bootsplash showing. You can't switch to another VT. You can, however, ssh in.
Nominating this as an Alpha blocker for its impact on lives: it's a conditional violation of "Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop." - https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria#Expected_image_boot_behavior . Quite often, the Workstation live images do not do that.
Ray says this commit fixes it:
and it should be in 3.15.91, which he's in the process of releasing right now.
gdm-3.15.91-1.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gdm-3.15.91-1.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Forgot to actually nominate as a blocker...
Bug is present in F22 Alpha TC7, however, update gdm-3.15.91-1.fc22 fixes the problem.
Discussed at today's blocker review meeting .
This bug was accepted as Alpha Blocker - This bug is a conditional violation of the following alpha criterion: "Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop."
gdm-3.15.91-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Did this bug make it into the alpha image?
I experience a bug like this with my Intel + Radeon notebook (Radeon is 2nd GPU) and I'm not sure if it's a new bug or this one.