How? 1510730 is about a crash when doing a useless edit that happens to be a crypto partition, this bug is about there being no way to use a crypto partition at all (regardless of the crash, that's easy enough to work around).
FWIW the work around for this bug ended up being:
* accept the guided encrypted+lvm layout
* do normal install
* boot off usb disk
* shrink ext4 + LV
* create new LV + FS I wanted (btrfs)
* "rsync -PavH --delete .../old/ .../new/"
* edit fstab
* delete old fs/LV
* resize new LV + btrfs reboot
The workaround for 1510730 is simply not to edit the crypto partition a second time.
> *** This bug is a duplicate of bug 1510730 *** /bugs.launchpad .net/bugs/ 1510730
> https:/
How? 1510730 is about a crash when doing a useless edit that happens to be a crypto partition, this bug is about there being no way to use a crypto partition at all (regardless of the crash, that's easy enough to work around).
FWIW the work around for this bug ended up being:
* accept the guided encrypted+lvm layout
* do normal install
* boot off usb disk
* shrink ext4 + LV
* create new LV + FS I wanted (btrfs)
* "rsync -PavH --delete .../old/ .../new/"
* edit fstab
* delete old fs/LV
* resize new LV + btrfs reboot
The workaround for 1510730 is simply not to edit the crypto partition a second time.