On Thu, Jul 03, 2025 at 12:38:32AM +0300, Konstantin Khomoutov wrote:
[...]
Do you have systemd-cryptsetup installed? (See the NEWS entry for
systemd=256-2, which I guess should be in the release notes too.)
>>
>> You need to install the systemd-cryptsetup binary package to let systemd
On Wed, Jul 02, 2025 at 01:10:16PM +0200, Guilhem Moulin wrote:
[...]
> > Hence I'm inclined to think it's still an "early boot" issue
>
> No it's not.
>
> >> Do you have systemd-cryptsetup installed? (See the NEWS entry for
> >> systemd=256-2, which I guess should be in the release notes too.)
On Wed, 02 Jul 2025 at 13:13:39 +0300, Konstantin Khomoutov wrote:
> On Wed, Jul 02, 2025 at 01:00:39AM +0200, Guilhem Moulin wrote:
>> I've noticed that the boot process brings up the LUKS2-encrypted root
>> parition just fine
>
> In my original mail I've mistakenly said "boot" there ^, but in fac
On Wed, Jul 02, 2025 at 01:00:39AM +0200, Guilhem Moulin wrote:
[...]
> > I've hit a regression after upgrading my Debian 12 laptop to Trixie -
> > in short, cryptsetup hangs at *early* boot stage when it apparently trying
> > to
> > create a device mapper node for a LUKS1 device it successfully
Hi,
On Wed, 02 Jul 2025 at 01:02:02 +0300, Konstantin Khomoutov wrote:
> I've hit a regression after upgrading my Debian 12 laptop to Trixie -
> in short, cryptsetup hangs at *early* boot stage when it apparently trying to
> create a device mapper node for a LUKS1 device it successfully opened.
>
Hi!
I've hit a regression after upgrading my Debian 12 laptop to Trixie -
in short, cryptsetup hangs at *early* boot stage when it apparently trying to
create a device mapper node for a LUKS1 device it successfully opened.
LUKS2 devices behave just fine.
I'm not sure what package to file a bug ag
6 matches
Mail list logo
