Created attachment 1256239 [details] Output of anaconda Description of problem: Attempting to install Fedora 25 from a live image on a USB flash drive on a Lenovo Thinkpad T60. Wayland can't handle the video card so trying the vnc install. This fails, and running anaconda manually from a command line shows the problem is that the anaconda scripts expect Metacity to be available. Version-Release number of selected component (if applicable): anaconda-25.20.8 How reproducible: Every time Steps to Reproduce: 1. Boot live image 2. Switch to console tty and log on 3. Run "anaconda --vnc" Actual results: VNC server starts (can remotely connect to it) but anaconda fails to start (so get blank screen and can't install system) Expected results: Anaconda starts as expected Additional info:
Created attachment 1256242 [details] system journal
I've now read the anaconda sources and it seems the choice of metacity is hard-coded (see the function doStartupX11Actions()). On the other hand, metacity hasn't been a default OS component for a long time (since the transition from GNOME 2 to GNOME 3). Given that, in my (uneducated) opinion it seems one of the following must be done: 1. Deprecate VNC installation. 2. Have the anaconda-core package depend on the metacity package. 3. Give anaconda a fallback when metacity is unavailable. If I'm totally off the mark I apologize and would love an explanation.
In general it is expected Anaconda will be started as a graphical application in the live environment via a desktop icon or via the liveinst script - using the anaconda command directly might or might not work. But I agree it should provide a better error message/warning in such a case. As for Metacity missing - it's not needed for the expected use case (graphical installation from the live environment), so Metacity and its dependencies are not part of the live image, which can then be smaller. I understand this sucks if the graphical environment does not work in your case, but there is a possible solution - the network installation image: https://download.fedoraproject.org/pub/fedora/linux/releases/25/Workstation/x86_64/iso/Fedora-Workstation-netinst-x86_64-25-1.3.iso The netinst image still uses X & Metacity and should have working VNC installation (as the network installation image is the expected usecase for it). You can even tell it to boot directly to VNC installation via boot options: http://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-vnc
Of course I started by trying VNC installation via boot options -- I only used the command directly in order to investigate the problem after the inst.vnc boot option didn't work. Now this use case (appending inst.vnc to the boot options) is specifically suggested by the <A HREF="https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/sect-vnc-installations-direct-mode.html">Fedora 25 Installation Guide</A>, so I don't think you can fairly dismiss it as "unexpected". I'll try netinst, but I think that either the installation guide needs to be changed to conform to what the LiveCD can do, or the LiveCD needs to be changed so that procedures suggested by the installation guide actually work.
For example, the installation guide can say at the beginning of Section 11 that VNC installation is only supported by the netinst image, not by the LiveCD.
(In reply to Lior from comment #5) > For example, the installation guide can say at the beginning of Section 11 > that VNC installation is only supported by the netinst image, not by the > LiveCD. Yes - that really looks like an omission in the docs. I'll clone this bug & assign it to the docs component so it can be fixed.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.