I can confirm Josh's description here on a desktop machine with
encrypted root and swap.

Booting today after 500 MB of updates from unstable yesterday yielded
the described behaviour.

After a reboot, the minute long delay was gone though there was still
some delay (say 5 seconds) and the message "/run/lvm/lvmetad.socket:
connect failed" was still present.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to