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.) > > You need to install the systemd-cryptsetup binary package to let systemd > automatically unlock your boot device. See #1079644 or #1076208.
Yes, your guess was a spot-on: installing cryptsetup-system fixed the issue completely for me. Looks like I'm going to propose an addition to the release notes as folks in the bugs you mentioned basically have hit the same problem. Thanks for helping me out, Guilhem!
