Bug 1451630
| Summary: | anaconda does not fall back to text mode for non-graphical systems | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Richter (Marvell) <rrichter> | ||||
| 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: | 26 | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, hannsj_uhl, jonathan, mkolman, pschindl, robatino, rrichter, rric, sgallagh, vanmeeuwen+fedora, vponcova | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | aarch64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedBlocker | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-07-17 12:31:46 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: | |||||||
| Attachments: |
|
||||||
|
Description
Robert Richter (Marvell)
2017-05-17 08:13:34 UTC
Proposed as a Blocker for 26-beta by Fedora user rric using the blocker tracking app because: Text mode installation of F26 would only work using a workaround. I have used Fedora-Server-dvd-aarch64-26-20170515.n.0.iso from here: https://dl.fedoraproject.org/pub/fedora-secondary/development/26/Server/aarch64/iso/ Tested on a Cavium CN88xx (ThunderX) Are there any logs in /tmp after the UI fails to start (& before you start Anaconda manually) ? That might help us debug what's happening. FYI, I'm +1 blocker under the "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." criterion. Well for a start this would need verifying on a release-blocking arch; aarch64 is not one. That criterion wasn't really written with the fallback mechanism in mind (in fact until this bug showed up I didn't know there *was* a fallback mechanism). It just means that these interfaces must work when used explicitly (by passing inst.text, for e.g.) Created attachment 1281101 [details]
log files from /tmp
Adding log files from /tmp
Discussed at 2017-05-22 blocker review meeting: [1]. This bug was rejected as Beta blocker: Right now this issue is only reported on non-blocking architectures. Please re-propose if it can be reproduced on a blocking install medium. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-05-22 Fixed in Fedora26:
Starting installer, one moment...
anaconda 26.21.11-1 for Fedora 26 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* when reporting a bug add logs from /tmp as separate text/plain attachments
21:45:11 X startup failed, falling back to text mode
================================================================================
================================================================================
VNC
1) Start VNC
2) Use text mode
Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to
refresh]: 2
================================================================================
================================================================================
Installation
1) [x] Language settings 2) [!] Time settings
(English (United States)) (Timezone is not set.)
3) [!] Installation source 4) [!] Software selection
(Processing...) (Processing...)
5) [!] Installation Destination 6) [ ] Network configuration
(No disks selected) (Connecting...)
7) [!] Root password 8) [!] User creation
(Password is not set.) (No user will be created)
Please make a selection from the above ['b' to begin installation, 'h' to help,
'q' to quit, 'r' to refresh]:
I got a report this is failing again: --- Starting installer, one moment... anaconda 26.21.11-1 for Fedora 26 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 * when reporting a bug add logs from /tmp as separate text/plain attachments (anaconda:2049): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0xaaab19fa82a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (anaconda:2049): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0xaaab19fa82a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (anaconda:2049): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0xaaab19fa82a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? --- Will try to reproduce. Here another workaround from pwhalen: "as a work around you can also specify 'text' in the kernel args which should also work as well" |