On Thu, Sep 4, 2025, at 1:47 PM, Brandon Werner wrote:
> Hello,
> A new partition.conf was added in the calamares-settings-debian package. In
> that file, there is a line "luksGeneration: luks2", which is installing
> forky/testing systems that cannot be booted by grub, dropping user to the
> grub prompt
Update: I tried installing a live encrypted system and installed the new grub
2.14 from sid, and still am unable to unlock a ssystem installed with luks2 and
Argon2. I saw in the release notes that grub 2.14 was supposed to support
Argon2 but posts online indicate other folks are having trouble as well. I
wonder if this luks2 support should be disabled until the grub package is fixed
upstream. Partition.conf also mentions problems with this luks2 configuration
in its comments.
> When partition.conf does not exist (as is in Trixie), this setting defaults
> to luks1. I read that grub has some support for unlocking luks2 partitions,
> however, I think it is not complete. This bug report has more information:
> https://savannah.gnu.org/bugs/?55093.
> The partition.conf file also includes a line "initialSwapChoice: none", which
> skips creating a swapfile on the installed live system. This is a change from
> Trixie which defaulted to creating a swapfile that was double or the same
> size as ram, depending on how much ram was installed in the users machine.
> The old behavior can be restored with "initialSwapChoice: suspend". I
> personally do not have a preference for the default choice of this setting. I
> decided to mention it, because I didn't notice an entry for it in the
> changelog, so I thought it might be an unintentional change. One data point I
> noticed while looking into this, is that the guided partitioning in Debian
> Installer creates a swap partition.
