GNU bug report logs - #55856
First LUKS passphrase prompt at Linux boot always fail

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#55856: closed (First LUKS passphrase prompt at Linux boot
 always fail)
Date: Tue, 14 Jun 2022 16:13:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 14 Jun 2022 12:12:49 -0400
with message-id <87zgifdy0u.fsf <at> gmail.com>
and subject line Re: bug#55856: First LUKS passphrase prompt at Linux boot always fail
has caused the debbugs.gnu.org bug report #55856,
regarding First LUKS passphrase prompt at Linux boot always fail
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
55856: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55856
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: First LUKS passphrase prompt at Linux boot always fail
Date: Wed, 08 Jun 2022 14:54:44 -0400

Hello,

It's something I've suffered for a while already on my desktop machine,
but I always assumed I was making a typo or something.

Today I confirmed that without first clearing the input buffer via
multiple backspaces strokes, the first LUKS passphrase (I have many
disks) *always* fail.

Perhaps some boot message or other text gets erroneously redirected to
the standard input and corrupts the user input.

Thanks,

Maxim

[Message part 3 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 55856-done <at> debbugs.gnu.org
Subject: Re: bug#55856: First LUKS passphrase prompt at Linux boot always fail
Date: Tue, 14 Jun 2022 12:12:49 -0400

Hey Ludo,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> Today I confirmed that without first clearing the input buffer via
>> multiple backspaces strokes, the first LUKS passphrase (I have many
>> disks) *always* fail.
>
> This is super weird (I’ve not observed that).  I don’t see how the input
> buffer could be filled with something else.  I wonder how this could be
> investigated!

Haha, this ended up being the HHKB Professional 2 USB keyword that was
hooked to my desktop.  Even when not using it, it appears that the small
USB hub that is built in the keyword sends noise to the line and causes
garbage to appear on stdin...

I should probably de-solder that near-useless thing from this otherwise
fine keyboard.

Thanks,

Closing.

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.