Description of problem: Fedora-17-Alpha live imaged failed to boot in 3 runlevel. Version-Release number of selected component (if applicable): Fedora-17-Alpha-i686-Live-Desktop.iso Fedora-17-Alpha-i686-Live-KDE.iso Steps to Reproduce: 1. Boot from CD. 2. Add "3" kernel parameter. 3. Actual results: No login on any of tty's. Expected results: Login should be shown for tty1-tty6 Additional info: It worked until last F17 nightly images but broken in Alpha.
The same result with "systemd.unit=runlevel3.target".
Try with "rd.plymouth=0 plymouth.enable=0 3"
Login shown with "rd.plymouth=0 plymouth.enable=0 3" and with "plymouth.enable=0 3" parameters.
I believe the problem is caused by firstboot-text.service. The service says: Conflicts=[...] plymouth-quit.service The result is that there is then nothing that would quit plymouth in multi-user.target.
Where did the firstboot in f17 get from? firstboot in f16 had firstboot-text.service removed, so I have no idea how it got back in f17.
Looking at the Koji build history ( http://koji.fedoraproject.org/koji/packageinfo?packageID=97 ), I see: firstboot-16.1-3.fc17 ausil 2012-01-13 20:38:50 complete firstboot-16.4-1.fc16 mgracik 2011-09-19 20:19:33 complete Maybe you had removed firstboot-text.service only on the f16 branch and forgot to update the master branch?
*** Bug 799312 has been marked as a duplicate of this bug. ***
Discussed at the 2012-03-02 blocker review meeting, as the 'original' of 799312. Agreed this is an F17 Beta blocker under criterion "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should provide a working login prompt without any unintended user intervention when boot is complete, and all virtual consoles intended to provide a working login prompt should do so". Re-opening because the update is still pending. Martin, you need to create an update via Bodhi for firstboot-17.0-1.fc17 and mark it as fixing this bug instead. Then when the update is pushed stable, this bug will get closed by Bodhi. Just firing a build through Koji isn't enough, it won't make it into the official tree unless you submit it as an update. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
firstboot-17.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/firstboot-17.0-1.fc17
Package firstboot-17.0-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firstboot-17.0-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2922/firstboot-17.0-1.fc17 then log in and leave karma (feedback).
TC2 should have the fixed firstboot, so we should be able to test and confirm this is fixed with TC2. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
TC2 boots in 3 runlevel (KDE i686 cd tested).
F17 Beta TC2 boots into runlevel 3 using KDE x86_64 live usb - setting to verified
We still have to push firstboot update to stable updates, please provide karma.
firstboot-17.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.