Description of problem: Can't launch installation process on netbook (can't press Begin Installation button because of low screen resolution 1024 x 600) Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQM1ZSRGVVMGdhakk/edit?usp=sharing
*** Bug 1144350 has been marked as a duplicate of this bug. ***
*** Bug 1156416 has been marked as a duplicate of this bug. ***
Éveryone who reported this problem: we need some more information about this. What media are you using? (Server? Workstation? a live spin? netinst? Alpha/Beta/etc?) And can you please provide some logs? There are log files in /tmp (you can get to a console by hitting Ctrl+Alt+F2): please attach them to this bug as individual, text/plain attachments. The ones we are most interested in are anaconda.log and X.log. If you are using a live environment (Workstation or one of the live spins), X.log won't be in /tmp but instead buried somewhere in the systemd journal. Running `journalctl -u gdm' provides the output from the Workstation live environment. Other live environments can probably do something similar. I just tried both Server and Workstation on a 1024x600 screen, and they worked fine for me. Server: https://dshea.fedorapeople.org/1135024-server.png Workstation: https://dshea.fedorapeople.org/1135024-workstation.png So I suspect that this may be a hardware-specific issue or a window manager providing a bad screen size or gtk doing something weird.
Created attachment 950599 [details] Anaconda log, after failure This is the anaconda log after I had run the installation up to the point where the buttons disappeard from the bottom right of the display.
Created attachment 950600 [details] X.log This is X.log, extracted using "journalctl -u gdm".
The system on which I have this problem is a Samsung N150 Plus. Anaconda actually starts out ok, in the "Welcome" and language selection screen the window size is correct and the buttons are visible at the bottom right. It is still ok when the installation dispatcher screen first comes up, the buttons are visible at the bottom right, as is the warning across the bottom of the screen about completing marked tasks. Going through Time Zone selection and Keyboard selection, the dispatcher screen is still correct each time it returns. But after going through the Disk partitioning task, and choosing "Manual Partitioning", when the dispatcher screen returns the warning and the buttons are gone from the bottom. I initially assumed this was a screen size problem, and that the buttons were gone off the bottom. This was probably a bad assumption on my part, based mostly on the fact that I have seen this kind of problem many times before. It may actually be that the buttons are simply gone (not displayed), rather than the window size being wrong. jw
More info - first, sorry, I forgot to add in the previous comment that this was done using the Workstation distribution, Beta RC1. The same problem existed with Workstation Beta TC4. More tests - I connected an external display (capable of up to 1280x1024), it was detected and configured automatically as 1024x768, with the netbook console still at 1024x600. I started Anaconda again, it came up on the external monitor, and everything worked normally, going through exactly the same process as the previous run, this time everything was visible and accessible as it should be. The installation is still running now, no doubt that it will finish without any further problem. jw
Thanks for the info. I'll take a closer look at this on Monday, but in case I get hit by a bus before then here's what I think is happening: Anaconda keeps all of its hub and spoke windows in a GtkStack, and any spoke that you've entered will still be kept on the stack even after you've left it. What's probably happening is that the custom partitioning spoke isn't scrollable in the right ways, so that ends up creating a window that's larger than your screen, and once it's been created and added to the stack gtk resizes everything on the stack to match that largest window. That window is always going to be pretty tall but hopefully we can stick a scrollbar in there without messing it up too much.
Created attachment 950747 [details] anaconda.log
Created attachment 950748 [details] X.log
Created attachment 950749 [details] demonstration
Acer Aspire One 521 $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0) 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 41) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 01:05.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RS880 HDMI Audio [Radeon HD 4200 Series] 02:00.0 Ethernet controller: Qualcomm Atheros AR8152 v1.1 Fast Ethernet (rev c1) 03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
(In reply to Mikhail from comment #11) > Created attachment 950749 [details] > demonstration "Custom partitioning selected," so I think we're on to something. Thanks.
Found an unexpected reproducer: the Lenovo X1 Carbon, after the 2x dpi scaling has been applied, has an effective resolution of 1280x770 which also has issues with the custom partitioning screen.
Proposed as a Blocker for 21-beta by Fedora user dshea using the blocker tracking app because: This is a violation of the F21 Alpha criterion, "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." This issue has been observed on systems with a display resolution of 1024x600 and systems with a hidpi resolution of 2560x1440. When using a display that does not have enough effective vertical pixels after hidpi scaling will be unable to complete the installation after entering either the custom partitioning or source selection spokes, due to the window being missized.
David: is the DPI scaling applied to a non-live install? In the live environment it can fairly easily be toggled off, which is an obvious workaround.
(In reply to Adam Williamson (Red Hat) from comment #16) > David: is the DPI scaling applied to a non-live install? In the live > environment it can fairly easily be toggled off, which is an obvious > workaround. Yes that is a feature that we provide for your convenience. Because otherwise the text is seriously tiny.
is there any kind of cmdline parameter to toggle it or anything? if not that's a bit unfortunate. the hidpi detection is not and probably cannot be 100%, which is one reason GNOME at least has a toggle in tweak-tool.
Are we still pretending that tweak tool is a real solution to anything? I mean, it's not even installed on the Workstation images. You can start the gtk inspector within anaconda and mess with the scale there, so I guess there's a workaround of about the same quality. Otherwise, no, there's no override. You'll get scaling and you'll like it.
it's still relatively easy to document 'yum install gnome-tweak-tool and run it'. Installing small packages into the live environment works fine, it uses a RAM-backed overlay fs, so it works till you run out of RAM.
Discussed in 2014-10-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-29/ Rejected as blocker. Low resolution is a known and documented shortcoming which we have not blocked on in the past.
I see what this already fixed, but latest beta still have this issue. Which build will include this update?
Depends when the anaconda team builds 21.48.14.
anaconda-21.48.14-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/anaconda-21.48.14-1.fc21
Package anaconda-21.48.14-1.fc21, python-blivet-0.61.9-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-21.48.14-1.fc21 python-blivet-0.61.9-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14928/python-blivet-0.61.9-1.fc21,anaconda-21.48.14-1.fc21 then log in and leave karma (feedback).
anaconda-21.48.14-1.fc21, python-blivet-0.61.9-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.