Bug 1003160
Summary: | 20 Alpha TC2 i386 Desktop Live boots to "Oh no!" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andre Robatino <robatino> |
Component: | distribution | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DUPLICATE | QA Contact: | Bill Nottingham <notting> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | dennis, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-02 07:34: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: | |||
Bug Depends On: | |||
Bug Blocks: | 980649 |
Description
Andre Robatino
2013-08-31 10:22:42 UTC
Proposing as Alpha Blocker according to https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Expected_image_boot_behavior : "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." My original testing was in KVM. Behavior in VirtualBox is essentially the same (in 32-bit, I see the "Oh no!", then the Try Fedora/Install to Hard Drive options, but if I click on "Try Fedora", I see the "Oh no!" again). I've also tested the 32- and 64-bit 20 Alpha TC2 Desktop Lives on bare metal as well - 32-bit fails in the same way on each of the 2 bare-metal platforms I tested, in addition to the report from John Reiser at https://bugzilla.redhat.com/show_bug.cgi?id=955779#c110 . 64-bit works on the one bare-metal platform I tested. I guess this should be move to something like gnome-shell. This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1002055 . Closing. *** This bug has been marked as a duplicate of bug 1002055 *** |