unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 55856-done@debbugs.gnu.org
Subject: bug#55856: First LUKS passphrase prompt at Linux boot always fail
Date: Tue, 14 Jun 2022 12:12:49 -0400	[thread overview]
Message-ID: <87zgifdy0u.fsf@gmail.com> (raw)
In-Reply-To: <87k09oxjly.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 11 Jun 2022 00:02:33 +0200")

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




      reply	other threads:[~2022-06-14 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 18:54 bug#55856: First LUKS passphrase prompt at Linux boot always fail Maxim Cournoyer
2022-06-10 22:02 ` Ludovic Courtès
2022-06-14 16:12   ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgifdy0u.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55856-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).