Bug 36629
Summary: | Mouseless GUI install broken | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alan Cox <alan> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2001-05-07 22:09:03 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: |
Description
Alan Cox
2001-04-19 11:58:24 UTC
When X fails to start, does it fall back to text mode or does the install exit abnormally? What I'm seeing on my test machine is that the installer just crashes. Maybe we shouldn't even start the X server if the mouse is not found. In my case it tries to run X a few times then aborts politely. It seems that at the point it aborts nicely it should have reverted to text mode even if it did try and start X Yes, it should fall back to text mode. There is code to do that...I'm not sure why it doesn't fall back to text mode. I will investigate further. |