installer crash on manual partitioning when using encryption

Bug #1931146 reported by JT Moree
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am attempting a fresh install on a dual boot setup. currently using windows 10 and Kubuntu 20.04. I am also using LUKS but the installer doesn't really seem to support it--even the old manual setup-- so I might have to downgrade to 20.10.

I have existing partitions so I choose manual but when I attempt to assign partitions and tell the system to format it crashes. In this case I was assigning /boot as a plain partition with nothing special and when clicking OK it crashes. I don't even get to the Install Now button. it crashes editing the /boot partition.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: KDE
Date: Mon Jun 7 16:24:34 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RebootRequiredPkgs: linux-image-5.11.0-18-generic
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
JT Moree (moreejt-pcxperience) wrote :
Revision history for this message
JT Moree (moreejt-pcxperience) wrote :

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
* start install
* move through setup to partitioning. choose manual
* choose one of the partitions and change it to use encryption
* choose another partition and click Edit. Choose to format and assign it as /boot'
* click OK and crash

summary: - installer crash on manual partitioning
+ installer crash on manual partitioning when using encryption
Revision history for this message
JT Moree (moreejt-pcxperience) wrote :

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 choose it as / then I can't install to it.

I tried clicking install now after assigning /boot and crypto but nothing happens.

Also, after doing the above steps if I click Back the installer crashes with 'An error occurred while creating the keyfile.'

Revision history for this message
JT Moree (moreejt-pcxperience) wrote :

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.

Another approach might be to manually mount /target on the crypto parts before install. Can we tell ubiquity to skip partitioning and just install to a mount point?

Revision history for this message
JT Moree (jtmoree) wrote :

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.

!!!! Be aware that another bug causes the installer to RECREATE existing LUKS partitions even if you CANCEL the install. DO NOT use ubiquity to manage crypto partitions for an install of Kubuntu/Ubuntu on existing LUKS partitions. Instead, use luksOpen yourself before running ubiquity.

Revision history for this message
JT Moree (jtmoree) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.