I can confirm that the issue is solved after running:
$ sudo apt-get -y install systemd-cryptsetup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on b
On Wed, Oct 16, 2024 at 07:38:26PM -, Eugene San wrote:
> Currently when installing using Calamares (Kubuntu, Lubuntu etc)
Ok thanks for this clarification.
> and probably Ubiquity (Mate etc)
There are no Ubuntu flavors that use ubiquity as their installer in Ubuntu
24.10.
--
You received
I have uploaded a proposed fix to oracular. As soon as the archive is
open for 25.04, I will upload the fix there, too.
** Changed in: systemd (Ubuntu Oracular)
Status: Triaged => In Progress
** Tags removed: rls-oo-incoming
--
You received this bug notification because you are a member
** Description changed:
+ [Test Plan]
+
+ 1. The systemd-cryptsetup package should be installed on upgrades from
+ Noble to Oracular:
+
+ $ lxc launch ubuntu:noble noble
+ $ lxc exec noble bash
+
+ Then, in the container:
+
+ $ cat > /etc/apt/sources.list.d/proposed.sources << EOF
+ Types: deb
@vorlon
Currently when installing using Calamares (Kubuntu, Lubuntu etc) and probably
Ubiquity (Mate etc), manual partitioning allows arbitrary number of luks
volumes including one them being /home.
Configurations with /home on luks which is not the first one, are "unbootable".
Configurations wi
On Wed, Oct 16, 2024 at 04:25:46PM -, Eugene San wrote:
> While I agree that moving systemd-cryptsetup to 'recommended' (or even
> 'depends') is the solution, it doesn't solve the issue with installs
> using LiveCDs.
We are discussing a stable release update to systemd which would raise
system
** Changed in: systemd (Ubuntu Oracular)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To manage notifica
While I agree that moving systemd-cryptsetup to 'recommended' (or even
'depends') is the solution, it doesn't solve the issue with installs
using LiveCDs.
Install ISOs must be updated to make systems with separate encrypted
/home bootable and systems with 2+ encrypted volumes usable.
Which projec
In 24.10, the systemd-cryptsetup tools were split into a separate
package[1]. The main systemd package has Suggests: systemd-cryptsetup
(rather than a stronger Recommends: relationship), and it is not
installed by default on installs/upgrades.
Installing systemd-cryptsetup sounds like the correct
I can confirm.
Not mounting luks volumes is not the only issue.
Among the issues are: very long boo times, inability to login using
graphical login managers and random hangs all over the place. Systems
with /home on separate encrypted location are completely broken even
with fresh installs.
The i
I ended up installing the package because systemctl status indicated my
system was in "maintenance" and that was probably the start of a chain
of issues (e.g. no audio). It fixed the issue for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
It looks like I'm facing the issue too on an upgrade from Noble to
Oracular. I haven't changed anything yet on purpose. Let me know if you
want me to try something. (meanwhile I'm going to debug pcscd's new use
of polkit to get my yubikey working again...)
--
You received this bug notification be
I can also confirm that the procedure described here has reliably solved
the problem for me.
Here is what I did in detail:
1. follow the official upgrade instructions (I used the console: 'sudo
do-release-upgrade -m desktop').
2. as soon as the upgrade has been completed, do NOT restart the comp
** Tags added: dist-upgrade oracular
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To manage notifications about
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
On
I can also confirm that installing `systemd-cryptsetup` fixed my slow
boot and unmounted crypt swap on my laptop with ZFS and full disk
encryption following the upgrade to 24.10. Thanks!
This is my `/etc/crypttab` setup by the Ubuntu 24.04 installer with
experimental ZFS + full disk encryption:
`
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To manage notific
I can confirm that installing the `systemd-cryptsetup` packages fixes
this. Thanks @jahu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To ma
See https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2084089
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To manage notifications ab
hi, same problem
apt-get -y install systemd-cryptsetup
solved problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084251
Title:
Only single LUKS device unlocked on boot
To manage notification
21 matches
Mail list logo
