Bug 798373
Summary: | live image failed to boot in 3 runlevel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | nucleo <alekcejk> |
Component: | firstboot | Assignee: | Martin Gracik <mgracik> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | awilliam, bcl, dmach, johannbg, kparal, metherid, mgracik, mschmidt, notting, plautrba, robatino, systemd-maint, tflink |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | firstboot-17.0-1.fc17 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-21 18:52:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 752649 |
Description
nucleo
2012-02-28 18:31:55 UTC
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. |