struck Linux mint 20.4 (focal, right?) - "just" lvm2 was removed though,
not cryptsetup.
I definitely did not remove lvm2 by hand but usually run autoremove.
Maybe I'll actually read the "these packages will be removed" next time
o_O
My setup was encrypted root, encrypted raid5 and none of those
Sorry all. Something happened while I was typing in the comment.
The bug has also affected me on Ubuntu 18.04.3 LTS. I finally fixed it
as described in comment #17.
Maybe unrelated but FYI. My installation is using UEFI but I need to
keep the bios in legacy mode and then select Ubuntu (UEFI) to
This bug has also affected me on Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
direct dependencies of ubiquity should not be autoremovable
To manage notifications about this
This bug was fixed in the package ubuntu-mate-meta - 1.253
---
ubuntu-mate-meta (1.253) eoan; urgency=medium
* Refreshed dependencies
* Added cryptsetup to core, desktop (LP: #11841672, #1801629)
* Added libnotify-bin to core-recommends, desktop-recommends
-- Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
direct dependencies of ubiquity should not be
This issue is still affecting Ubuntu MATE 19.10 beta. See the following
for more detail:
* https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1841672
** Also affects: xubuntu-meta (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
** Also affects: ubiquity (Ubuntu Eoan)
Julian verified this as not reproducing on disco now, with the livecd-
rootfs change. Closing the ubiquity task as invalid.
** Changed in: ubiquity (Ubuntu Disco)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
direct dependencies of ubiquity should not be autoremovable
To
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
direct dependencies of
Fix is verified, daily images of xubuntu disco as of today do not
produce the issue anymore :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801629
Title:
direct dependencies of ubiquity should
This seems to have affected me even though I never ran autoclean. Maybe
apt autocleans after I've used it to install things enough times? No
idea. Was saved by this answer: https://askubuntu.com/a/1120949/69057
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package livecd-rootfs - 2.566
---
livecd-rootfs (2.566) disco; urgency=medium
[ Julian Andres Klode ]
* Do not mark direct dependencies of ubiquity as auto installed. This caused
cryptsetup to remain auto on the installed system (LP: #1801629)
[
** Summary changed:
- xubuntu-core needs to depend on cryptsetup and lvm2 or 'apt autoremove' will
make a LUKS+LVM encrypted root partition non-bootable
+ direct dependencies of ubiquity should not be autoremovable
--
You received this bug notification because you are a member of Ubuntu
Bugs,
13 matches
Mail list logo
