Ubiquity installer crashes when editing manual crypto partition

Bug #1510730 reported by David Schoen on 2015-10-27
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
High
Unassigned

Bug Description

Using the Kubuntu 15.10 AMD64 iso.

After selecting to create a manual partition layout, adding a primary /boot (sda1) and a logic crypto by selecting "physical volume for encryption" (sda5), if I select the crypto volume and click "Change...", make no changes and click "OK" ubiquity crashes with:
Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartMan.py", line 453, in on_edit_clicked
    self.partman_edit_dialog(devpart, partition)
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartMan.py", line 367, in partman_edit_dialog
    self.ctrlr.dbfilter.edit_partition(devpart, **edits)
  File "/usr/lib/ubiquity/plugins/ubi-partman.py", line 3289, in edit_partition
    assert self.current_question == 'partman/choose_partition'
AssertionError

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity 2.21.37
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.365
CurrentDesktop: KDE
Date: Tue Oct 27 23:48:21 2015
InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi
LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

David Schoen (neerolyte) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Changed in ubiquity (Ubuntu):
status: New → Incomplete
tags: added: ident-mismatch
David Schoen (neerolyte) wrote :

I verified the sha256sum of the kubuntu-15.10-desktop-amd64.iso, it's fine.

The iso isn't burnt to CD/DVD it's been put on a usb using usb-creator-gtk.

Booting the USB and using it's self check (i.e typing "check" at the initial "boot: " prompt) checks all the files and confirms "Check finished: no errors found".

I'm unable to perform the check at https://help.ubuntu.com/community/Installation/CDIntegrityCheck (because of https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1325801 ) , but I believe it's the same as running "check" manually(?).

David Schoen (neerolyte) wrote :

I can reproduce this by booting a verified copy of kubuntu-15.10-desktop-amd64.iso in a Virtualbox VM. It crashes just like the physical hardware does booting off the USB key.

Changed in ubiquity (Ubuntu):
status: Incomplete → New
Changed in ubiquity (Ubuntu):
importance: Undecided → High

Hi! I have exactly the same issue with kubuntu 16.04 :-(. But Ubuntu 16.04 installer works fine. I have tested both distribution on VirtualBox.

Andreas Krüger (kubdteu1) wrote :

I had a very similar experience this morning when attempting to install a USB stick based on xubuntu-16.04.1-desktop-amd64.iso :

I added /dev/sdb1 for /boot

I added /dev/sdb2 and asked it to become the base of an encrypted volume.

My intention was to use /dev/mapper/sda2_crypt as a physical volume for LVM, and later split that up into root, swap, and a bit of free space for snapshots (which I tend to use for backup).

In my case, the /dev/mapper/sda2_crypt was created, and it was pre-configured as a file system. I had never said anything about wanting a file system on top of that, so that's already a bug.

Worse: When using the UI to change that to "basis for LVM", while several different file system types are offered, "physical volume for LVM" isn't.

So I cannot proceed with my installation as planned.

FWIW: I did run "check" on the USB stick, it found no problems.

Andreas Krüger (kubdteu1) wrote :

How does one correct a mistake in a comment? I should have written: "... when I wanted to install from a USB stick based on xubuntu-16.04.01-desktop-amd64.iso".

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed

My $0.02. This is a show-stopping bug. We are trying to roll out some new desktops configured to CIS hardening standards including the required encryption and separate partitions and this makes it nearly impossible to achieve.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers