[Bug 1801629] Re: direct dependencies of ubiquity should not be autoremovable

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~juliank/livecd-rootfs/+git/livecd-rootfs/+merge/363932

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1801629

Title:
  direct dependencies of ubiquity should not be autoremovable

Status in OEM Priority Project:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Invalid
Status in ubuntu-mate-meta source package in Bionic:
  Invalid
Status in xubuntu-meta source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Cosmic:
  Won't Fix
Status in ubiquity source package in Cosmic:
  Won't Fix
Status in ubuntu-mate-meta source package in Cosmic:
  Invalid
Status in xubuntu-meta source package in Cosmic:
  Invalid
Status in livecd-rootfs source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Triaged
Status in ubuntu-mate-meta source package in Disco:
  Invalid
Status in xubuntu-meta source package in Disco:
  Invalid

Bug description:
  In a clean install of Xubuntu 18.10, if an unsuspecting user runs 'apt
  autoremove', it will remove 'cryptsetup' and 'lvm2' making the system
  non-bootable at next restart if an encrypted(LUKS+LVM) root partition
  was selected during the ubiquity installer wizard:

  $ sudo apt update && sudo apt --auto-remove full-upgrade && cat /run/reboo*
  <snip...>
  The following packages will be REMOVED:
    cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
  <...snip>

  This _will_ make the system non-bootable upon restart if LUKS+LVM are
  active on the root partition. This would, by extension, make any auto-
  mounted partitions(home, etc.) unavailable after boot as well!

  WORKAROUND:

  $ sudo apt install cryptsetup lvm2
  <snip...>
  cryptsetup is already the newest version (2:2.0.4-2ubuntu2).
  cryptsetup set to manually installed.
  lvm2 is already the newest version (2.02.176-4.1ubuntu3).
  lvm2 set to manually installed.
  <...snip>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xubuntu-core 2.227
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 18:20:38 2018
  InstallationDate: Installed on 2018-11-04 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1801629/+subscriptions