User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build Identifier: I have successfully installed Fedora 22 Workstation using Fedora-Live-Workstation-i686-22-3.iso using livesub-creator on a Lenovo T60p laptop with an ATI Radeon RV530 graphics card. However, on first boot the login page is simple coloured streaks with no recognisable image. Using the workaround in the Fedora forum for F22 beta issues, I edited the Grub command line on the fly to add "nomodeset" to the boot command - which apparently forces the login screen to be displayed using X rather than Wayland. The same forum post indicates editing /etc/gdm/custom.conf and uncommenting #WaylandEnable=false. In this mode, Fedora 22 works perfectly over the last few days, but it is clearly using X rather than Wayland. Reproducible: Always Steps to Reproduce: 1.Install Live-Workstation-i686-22-3.iso using livesub-creator on a Lenovo T60p laptop with an ATI Radeon RV530 graphics card. 2.At the end of the installation, reboot as instructed 3. Actual Results: You will not be able to login because the login page is not readable Expected Results: I got a screen full of coloured streaks rather than a login page Displayed the standard login page. My issue does seem to be somewhat related to 1218787 - which I read as, the fallbak from Wayland to X on firstboot does not work.
initial-setup is the utility that runs on non-GNOME installations and finishes the system configuration after the installation. This seems like an issue in GDM (the login screen) or wayland. Reassigning.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.