Created attachment 1452825 [details]
Description of problem:
boot the installer with inst.vnc inst.vncpassword,the system will just hang there as shown in the attached screenshot,but if you just add the inst.vnc option,
the installer will be able to finish the installation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 1452826 [details]
Please attach all the logs from the tmp/*.log.
Created attachment 1452859 [details]
Created attachment 1452860 [details]
Created attachment 1452861 [details]
Created attachment 1452862 [details]
Created attachment 1452863 [details]
Created attachment 1452864 [details]
Still see this bug with the latest Fedora-Workstation-netinst-x86_64-Rawhide-20180623.n.1.iso and Fedora-Server-dvd-x86_64-Rawhide-20180623.n.1.iso
Also happens after setting a password on a text install (Fedora-Rawhide-20180707.n.2)
1) Start VNC
2) Use text mode
Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to
Please provide VNC password (must be six to eight characters long).
You will have to type it twice. Leave blank for no password
11:15:44 Starting VNC...
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
Still happens with latest Fedora-Workstation-netinst-x86_64-29-20180901.n.0.iso
Proposed as a Blocker for 29-beta by Fedora user lnie using the blocker tracking app because:
This seems affects the criteria:
When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
I think I'd be -1, the criterion doesn't require that this specific feature (passworded VNC) work, and regular VNC without password works fine, I think.
Discussed at 2018-09-13 Fedora 29 Beta Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-09-13/f29-beta-go_no_go-meeting.2018-09-13-17.00.html . Rejected as a blocker, as the criteria does not say anything about requiring password-protected VNC to work, only 'VNC'. inst.vnc works fine.
Obviously it'd still be desirable to fix this, but it doesn't seem to meet the requirements to be a blocker.
*** Bug 1631093 has been marked as a duplicate of this bug. ***
Fixed in the pull request: https://github.com/rhinstaller/anaconda/pull/1617
Anaconda with the fix fails with an error that is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1631483
Created attachment 1488073 [details]
.treeinfo from Fedora rawhide of 2018-09-19
lnie, can you check if this is working correctly in current Rawhide? Thanks!
VNC password option confirmed working with a text install of Fedora-Rawhide-20190217.n.0
Then we can go ahead and close this, nothing else is needed. Thanks!