bug#55856: closed (First LUKS passphrase prompt at Linux boot always fail)

[GNU bug Tracking System]

Your message dated Tue, 14 Jun 2022 12:12:49 -0400
with message-id <87zgifdy0u.fsf@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@gnu.org.)


-- 
55856: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55856
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> 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
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#55856: First LUKS passphrase prompt at Linux boot always fail
>
>
>
>
> Date: 
>
> Tue, 14 Jun 2022 12:12:49 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
>
>
>
>
> Hey Ludo,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> > Hi,
> >
> > Maxim Cournoyer <maxim.cournoyer@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
>
>
> --- End Message ---