[Bug 2051478] Re: unlock passphrase doesn't work in plymouth but works in recovery mode

[Nobuto Murata]

By downgrading plymouth from 23.360.11-0ubuntu2 to 22.02.122-4ubuntu2 by
hand, the passphrase worked so it's a plymouth issue rather than
cryptsetup, it seems.

https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/libplymouth5_22.02.122-4ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth_22.02.122-4ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-label_22.02.122-4ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-spinner_22.02.122-4ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-ubuntu-text_22.02.122-4ubuntu2_amd64.deb


** Also affects: plymouth (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cryptsetup (Ubuntu)
       Status: New => Invalid

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

Title:
  unlock passphrase doesn't work in plymouth but works in recovery mode

Status in cryptsetup package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  New

Bug description:
  The system suddenly stopped accepting the existing passphrase on boot.
  However, the passphrase is definitely correct since the same one can
  be used in the recovery mode and it unlocks the volume appropriately.

  I'm not sure which recent update brought this behavior.

  Last successful graphical boot: 2024-01-28 00:43:09 +0900

  Fwiw, the existing passphrase was long enough and contains some
  special characters such as "!". The confusing part is shorter
  passphrase but with "!" seems to work.

  WORKAROUND:
  1. boot into the recovery mode
  2. unlock the volume in the console
  3. add a new key with `cryptsetup luksAddKey /dev/nvme0n1p3`
     or remove "splash" from /etc/default/grub and run `update-grub`
  3. reboot

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: cryptsetup 2:2.6.1-6ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 15:41:03 2024
  InstallationDate: Installed on 2024-01-08 (21 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=<set>SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks

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