[Bug 1841672] Re: CryptSetup packages should not be removed by `apt-get autoremove` on system installed with encryption and LVM

[Michael Hudson-Doyle]

That said, it does seem attempts have been made to fix it in livecd-
rootfs before. I wrote this https://git.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-
rootfs/commit/?id=b235dfb718730a0a83fec0a1b366ddef8468a0b5 but I'm not
sure about landing this in the space between now and release unless
there are flavours that are still affected.

We should fix this properly (i.e. by having ubiquity itself mark
cryptsetup as manual) in the next cycle though.

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

Title:
  CryptSetup packages should not be removed by `apt-get autoremove` on
  system installed with encryption and LVM

Status in cryptsetup package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Eoan:
  Invalid
Status in livecd-rootfs source package in Eoan:
  Invalid
Status in ubiquity source package in Eoan:
  Confirmed
Status in ubuntu-mate-meta source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10 MATE with Encryption and LVM
  2. Ensure that it boots after install
  3. Run `sudo apt autoremove`

  Expected results:
  * there are no packages to remove

  Actual results:
  * it tries to remove cryptsetup:

  $ sudo apt autoremove
  [sudo] password for mate:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run
  0 upgraded, 0 newly installed, 4 to remove and 23 not upgraded.
  After this operation, 1 178 kB disk space will be freed.
  Do you want to continue? [Y/n]

  and this will lead on un-bootable encrypted system.
  This is very unexpected and dangerous.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cryptsetup 2:2.2.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 27 23:55:09 2019
  InstallationDate: Installed on 2019-08-27 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190827)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash
  crypttab: sda5_crypt UUID=784fac4b-d7a4-4e62-b57e-7ce01e8b0160 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1841672/+subscriptions