*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
Hi Paolo,
I say bug feels like the same because while booting LUKS is not asking
for password.
I upgraded from 24.04 to 24.10 and also did a fresh install without any
success.
I managed to solve the problem by installing this missing package:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251/comments/1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084802
Title:
LUKS not asking for password at boot after upgrading to 24.10
Status in linux package in Ubuntu:
New
Bug description:
This bug feels like the same of this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998266 but for
24.10.
Someone have already asked for this here:
https://askubuntu.com/questions/1529983/the-luks-passphrase-screen-
doesnt-show-up-after-24-10-installation
My situation is exactly the same.
My /etc/fstab:
UUID=A4BE-EBF0 /boot/efi vfat defaults 0
2
UUID=cc9279a3-e6a5-4d3a-9e96-968b567d84d2 / ext4 defaults 0
1
/dev/mapper/homecifrado /home ext4
defaults 0 2
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs
defaults,noatime,mode=1777 0 0
/etc/crypttab:
homecifrado UUID=6cbae53c-0312-4c15-a95c-f37772a9e9fc none luks
/etc/cryptsetup-initramfs/cryptroo.conf:
target=homecifrado
source=6cbae53c-0312-4c15-a95c-f37772a9e9fc
/etc/cryptsetup-initramfs/conf-hook:
#
# Configuration file for the cryptroot initramfs hook.
#
#
# KEYFILE_PATTERN: ...
#
# The value of this variable is interpreted as a shell pattern.
# Matching key files from the crypttab(5) are included in the initramfs
# image. The associated devices can then be unlocked without manual
# intervention. (For instance if /etc/crypttab lists two key files
# /etc/keys/{root,swap}.key, you can set KEYFILE_PATTERN="/etc/keys/*.key"
# to add them to the initrd.)
#
# If KEYFILE_PATTERN if null or unset (default) then no key file is
# copied to the initramfs image.
#
# Note that the glob(7) is not expanded for crypttab(5) entries with a
# 'keyscript=' option. In that case, the field is not treated as a file
# name but given as argument to the keyscript.
#
# WARNING:
# * If the initramfs image is to include private key material, you'll
# want to create it with a restrictive umask in order to keep
# non-privileged users at bay. For instance, set UMASK=0077 in
# /etc/initramfs-tools/initramfs.conf
# * If you use cryptsetup-suspend, private key material inside the
# initramfs will be in memory during suspend period, defeating the
# purpose of cryptsetup-suspend.
#
#KEYFILE_PATTERN=
#
# ASKPASS: [ y | n ]
#
# Whether to include the askpass binary to the initramfs image. askpass
# is required for interactive passphrase prompts, and ASKPASS=y (the
# default) is implied when the hook detects that same device needs to be
# unlocked interactively (i.e., not via keyfile nor keyscript) at
# initramfs stage. Setting ASKPASS=n also skips `cryptroot-unlock`
# inclusion as it requires the askpass executable.
ASKPASS=y
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
