Created attachment 1545037 [details] version luks1 after passphrase popup Description of problem: Version-Release number of selected component (if applicable): 30.25-3-3.fc30 from Fedora-Workstation-netinst-x86_64-30-20190315.n.0.iso How reproducible: always Steps to Reproduce: 1. Start Boot ISO, choose Language "English" -> Installation Summary overview -> (click) "System -> Installation Destination" 2. Device Selection: Storage Configuration: (choose radio-button) "custom" -> (enable checkbox) "Encrypt my data" -> (click) "Done" 3. enter a passphrase in the popup 4. Manual Partitioning: (LVM is set as partitioning scheme) -> (click) "+" symbol to add a new mount point, input "/" -> (click) "Add mount point" The result will be the screenshot with "luks1" as set LUKS version 5. Having the intention to use luks2, change LUKS version in dropdown to "luks2", (click) Update Settings Actual results: The LUKS version will set itself back to "luks1". Expected results: "luks2" Additional info: I speculate setting the passphrase in step (3) will default to luks1. If the checkbox "Encrypt" next to Device Type LVM is (unselected) and later (re-selected) while having set "luks2" as Version, (clicking) Update settings will leave it at "luks2". It works the otherway too - whatever version was set while enabling the "Encrypt" checkbox will be enforced when trying to change the LUKS version later individually. My suggestion: 1. set luks2 as default version for first passphrase popup at step (3) 2. in manual partitioning overview, transform "Encrypt" checkbox next to "Device Type" to a Dropdown of "no encryption, Encrypt (luks1), Encrypt (luks2)" and remove the individual version dropdown or gray-out enabled LUKS version dropdown after "update settings"
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1899
Created attachment 1546037 [details] luks-version-dropdown-behaviour video walkthrough to dropdown behaviour
anaconda-30.25.4-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f36d739dc
We still need to fix the menu for the LUKS version.
anaconda-30.25.4-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f36d739dc
anaconda-30.25.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Created attachment 1683435 [details] Another luks1/luks2 confusion Attaching another reproducer for incorrectly displayed version of luks. Fedora-Server-netinst-x86_64-Rawhide-20200428.n.0.iso anaconda-33.11-1.fc33
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.