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 because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2084251 Title: Only single LUKS device unlocked on boot Status in cryptsetup package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cryptsetup source package in Oracular: Confirmed Status in systemd source package in Oracular: Confirmed Bug description: Hi, I just upgraded from Noble to Oracular. It seems post-upgrade, only a single LUKS device is decrypted on boot. My `/etc/crypttab` is as follows: | nvme0n1p3_crypt UUID=c82c8c6c-e363-473f-a655-a325d4e6cf3b none luks,discard | nvme0n1p4_crypt UUID=3de219b7-3e0c-437b-a0eb-d3cb8087d74e none luks,discard `lsblk -o +UUID` showing UUIDs: | ├─nvme0n1p3 259:3 0 384G 0 part c82c8c6c-e363-473f-a655-a325d4e6cf3b | │ └─nvme0n1p3_crypt 252:0 0 384G 0 crypt / f48e2583-013f-474c-9f57-5deabef8d833 | └─nvme0n1p4 259:4 0 546.8G 0 part 3de219b7-3e0c-437b-a0eb-d3cb8087d74e | └─nvme0n1p4_crypt 252:1 0 546.7G 0 crypt /home dfea2d4c-f43e-4ef9-8938-3255f7987dfa I can confirm that the `crypttab` entry is correct because I can run `cryptdisks_start nvme0n1p4_crypt` on the recovery prompt and it decrypts it. I haven't yet tried downgrading `cryptsetup`, will give that a try tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
