Bug 1015053
Summary: | Unable to boot a fresh installed F20-Beta-TC1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | amulhern, anaconda-maint-list, dshea, g.kaviyarasu, joachim.backes, jonathan, mkolman, sbueno, vanmeeuwen+fedora, vpodzime |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-17 08:24:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Backes
2013-10-03 11:32:47 UTC
Still the same effect with TC2! But if booting into runlevel 3, this is possible. Then logging in as root and starting "init 5" will present the graphical GDM login! After have logged in, gnome-shell runs. If booting into runlevel 3 works, it's probably not an anaconda issue. It seems like the X server fails to start or something like that. What exactly happens if you try to boot to runlevel 5 (default)? Booting F20-Beta-TC4 in VirtualBox VM boots fine, both with and without explicit given runlevel (5 for example) as kernel boot parameter. So I think the described effect is only a buggy behaviour of TC1 or TC2. You may close the BZ. |