Ubiquity crashes installing to encrypted partition

Bug #1409557 reported by Stephen Early
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Attempting to install Ubuntu 14.10 alongside Windows 8.1 on a Lenovo Y50-70. Want / and swap to be encrypted. Used gparted to resize the main Windows 8.1 partition to make space for Ubuntu, then started ubiquity.

Chose "something else" partitioning because the "encrypt" and "use lvm" checkboxes are greyed out when "install Ubuntu alongside Windows Boot Manager" is selected. Created an ext2 partition of 512Mb for /boot in the free space. Created an encrypted partition. Noticed that it automatically created an ext4 filesystem within this, so clicked "Revert" which got rid of the ext4 filesystem but left the /dev/mapper/sda9_crypt device in place. Clicked "New Partition Table" on this, which appeared to work, and then created swap and ext4 root filesystem within it.

Ubiquity crashed on clicking Install Now.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CasperVersion: 1.345
Date: Sun Jan 11 22:47:12 2015
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Stephen Early (steve-greenend) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This isn't a Critical bug. By this I don't mean I think it's unimportant, just that given that it's not part of the default paths for install, I think we can classify it as a lower priority.

I'm hoping this isn't the actual cause for the crash since I'd hope this is already appropriately handled by ubiquity, but since it came up in the logs:
Jan 11 22:46:59 ubuntu ubiquity: cat: 0-667046379519/mountpoint
Jan 11 22:46:59 ubuntu ubiquity: : No such file or directory
Jan 11 22:46:59 ubuntu ubiquity[4539]: debconffilter_done: ubiquity.components.partman_commit (current: ubi-timezone)
Jan 11 22:47:00 ubuntu ubiquity: Traceback (most recent call last):
Jan 11 22:47:00 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 747, in <module>
Jan 11 22:47:00 ubuntu ubiquity: install = Install()
Jan 11 22:47:00 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 72, in __init__
Jan 11 22:47:00 ubuntu ubiquity: 'Failed to mount the target: %s' % str(self.target)
Jan 11 22:47:00 ubuntu ubiquity: AssertionError: Failed to mount the target: /target

Could you confirm there was indeed a partition marked as the mountpoint for / ? It's not something which is usually missing, but it would be nice to have a confirmation of the exact partitioning if possible. A screenshot of the partitioning dialog before confirming would be the best way to describe this.

Thanks!

Changed in ubiquity (Ubuntu):
importance: Critical → Medium
status: Confirmed → Incomplete
Revision history for this message
Stephen Early (steve-greenend) wrote :

There was a partition marked as the mountpoint for / in the Ubiquity user interface. It would have been the ext4 filesystem within the "New partition table" within the sda9_crypt device.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.