Lubuntu installer crashes when choosing LVM encrypted disk

Bug #1743439 reported by Kyle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

A fresh install of 18.04 using Try Lubuntu, change resolution to 1440x900, sudo swapoff -a, then install from the desktop. For partitioning, choose encrypted disk which turns on LVM. The installer fails. I believe the only option was "OK" which returns me to the partioning dialog. Turn off LVM which turns off encrypted disk (even though I need it to be encrypted), click Next, and the installer crashes causing this submit bug report browser window to open.

Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
ubiquity:
  Installed: 17.10.10
  Candidate: 17.10.10
  Version table:
 *** 17.10.10 500
        500 cdrom://Lubuntu 18.04 LTS _Bionic Beaver_ - Alpha amd64 (20180115) bionic/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CasperVersion: 1.388
Date: Mon Jan 15 18:38:06 2018
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180115)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kyle (n-kyle) wrote :
Revision history for this message
Kyle (n-kyle) wrote :

Additional Details

The ISO I am using is bionic-desktop-amd64.iso which for me is dated Jan 01, 2018.
I can recreate the bug using a virtual machine.

I made a 2 minute video that demonstrates from boot to the crash that creates the data submitted here.

https://youtu.be/htFL03ZEY7c
https://www.youtube.com/embed/htFL03ZEY7c (Full screen)

I can upload the file as an attachment if the community prefers that. I hope this helps.

-Kyle

Revision history for this message
Kyle (n-kyle) wrote :

Please forgive the typographical error in comment #2. The date is Jan 14, 2018 for my ISO.

-Kyle

Revision history for this message
accnetdev (accnetdev) wrote :

Hi,
Crash here with daily build of 2018/02/14.
Without LVM selected at initramfs operations at the end of installation.
Can't install it on Virtualbox VM.

Revision history for this message
accnetdev (accnetdev) wrote :

Do you thing it would be better to open a new bug ?

More details on the issue in trying to install Lubuntu Next 18.04 daily build of 20180215 (same as previously).

The error before the Installer Crash (I translate from french) :

Error when removing initramfs-tools

intalled initramfs-tools package post-installation script subprocess
returned error exit status 1

I installed with no LVM, no update selected and common options.

---

I wrote :

"Hi,
Crash here with daily build of 2018/02/14.
Without LVM selected at initramfs operations at the end of installation.
Can't install it on Virtualbox VM."

Revision history for this message
Kyle (n-kyle) wrote :

It was suggested that this bug is a duplicate of 1638420 https://bugs.launchpad.net/bugs/1638420 but it is not. The bug 1638420 still exists in the 18.04 installer the last time I checked.

It is because of bug 1638420 that we end up using the < Back button, and change the Installation Type. That is when the installer crashes (bug 1743439).

1638420 is about the installer missing required components for LVM encrypted disk.
1743439 is about the installer crashing when you change the Installation Type.

Again the video demonstrates this: https://www.youtube.com/embed/htFL03ZEY7c

Fixing bug 1638420 may mitigate 1743439 because users will not fail the encrypted install and require them to go back and switch the Installation Type, but they are separate issues.

-Kyle

Revision history for this message
Kyle (n-kyle) wrote :

I grabbed the release installer and ran some tests this morning. It appears bug 1638420 has been fixed. Because of that, I was not able to make bug 1743439 happen. I'm not sure 1743439 was actually corrected, but since we can no longer reproduce the issue, I think we can mark 1743439 closed.

-Kyle

Phillip Susi (psusi)
Changed in ubiquity (Ubuntu):
status: New → Fix Released
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.