Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 review silently freezes on patatt fail
Date: Sun, 12 Jul 2026 12:22:27 +0100	[thread overview]
Message-ID: <alN2yOZmbl31BfVW@lucifer> (raw)

Hi Konstantin,

I noticed a bug in b4 review (as pinged on fedi but better to send the bug
report properly :)

So I had an incorrect configuration locally - my signing key in git (git config
user.signingKey) was set to the wrong one (the old, revoked one, the one
I... err... lost the private key for :P).

And with this in place, I was using b4 review tui --email-dry-run to experiment
with composing a reply.

The replying bit worked fine. But when I hit 'S' to send it froze up. No error
shown, just frozen.

Some strace's later and I identified that gpg (of course) was to blame - it
seems the python code just hangs waiting forever (idle event loop looks like).

And it seems to be when it tried to use patatt to sign my reply to a mail, gpg
failed with exit code 2:

execve("/usr/bin/gpg", ["gpg", "--batch", "--no-auto-key-retrieve",
"--no-auto-check-trustdb", "-s", "-u", "130EC0891A27271B"]) = 0
exit_group(2)

(I can give you a full strace if you need!)

I confirmed this was the signing for sure as passing --no-sign fixed it.

Once I updated my signing key to the correct one, everything worked fine.

$ b4 --version
0.15.2

Cheers, Lorenzo

                 reply	other threads:[~2026-07-12 11:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=alN2yOZmbl31BfVW@lucifer \
    --to=ljs@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox