https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1264813
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931146
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1904270
--
You received this bug notification
This may be a duplicate of an eight year old bug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731. The
workaround is to use the gtk_ui
1. Install ubiquity-frontend-gtk;
2. run "ubiquity gtk_ui"
options are not exactly the same but close enough to get install with
LUKS root.
FYI. I can install if I create LVM volumes on top of the crypto part
but bootup with LVM and LUKS is complex so it fails. This is probably
not the fault of the installer but I'm still working on that approach as
a workaround to not having direct access to the crypto part in the
installer.
When I manually create the luks partition and label it as such ubiquity
crashes when I then try to setup /boot. If I setup /boot first it does
not crash and I can then assign a crypto partition. But that's it. The
installer will not let me do anything else with a crypo partition. If I
cannot
I just ran an install where I don't use LUKs and it works. seems that in
addition to the installer not allowing me to fully configure encrypted
partitions it also crashes configuring other partitions when one of them is set
to use encryption.
to reproduce
* create partitions before install
*
