Am Fr., 24. Aug. 2018 um 23:39 Uhr schrieb Guilhem Moulin :
>
> Control: tag -1 moreinfo
>
> On Fri, 24 Aug 2018 at 22:45:40 +0200, Matthias Klumpp wrote:
> > Obviously no Plymouth was shown here. The log looks normal to me.
>
> Ah right, plymouthd isn't started yet when you're dropped into the
>
Control: tag -1 moreinfo
On Fri, 24 Aug 2018 at 22:45:40 +0200, Matthias Klumpp wrote:
> Obviously no Plymouth was shown here. The log looks normal to me.
Ah right, plymouthd isn't started yet when you're dropped into the
initramfs shell, so you'll need to start it manually:
Am Fr., 24. Aug. 2018 um 19:09 Uhr schrieb Guilhem Moulin :
>
> Hi,
>
> On Fri, 24 Aug 2018 at 18:49:10 +0200, Matthias Klumpp wrote:
> > This issue is really annoying, and I would be glad for any pointers on
> > how to investigate the issue further, as I am no expert on cryptsetup.
>
> See
Hi,
On Fri, 24 Aug 2018 at 18:49:10 +0200, Matthias Klumpp wrote:
> This issue is really annoying, and I would be glad for any pointers on
> how to investigate the issue further, as I am no expert on cryptsetup.
See https://wiki.debian.org/CryptsetupDebug to trace
/scripts/local-top/cryptroot,
Package: cryptsetup-initramfs
Version: 2:2.0.4-2
Severity: normal
Hi!
First of all, this bug appears on PureOS and I am currently working on
testing it on Debian as well. However, the issue started to appear at
the time cryptsetup was updated with massive changes in June, so I am
reasonably
5 matches
Mail list logo
