Problem
rbw register prompts for client_id and client_secret via two sequential pinentry dialogs. With pinentry-gnome3, each dialog grabs focus and the next one opens immediately after the previous is dismissed. This makes it impossible to switch to another window to copy the client_secret after entering the client_id.
Steps to reproduce
- Configure rbw with
pinentry-gnome3
- Run
rbw register
- Enter
client_id in the first GNOME pinentry dialog and confirm
- The second dialog (for
client_secret) opens immediately
- There is no opportunity to switch to the browser/vault to copy the
client_secret
Expected behavior
The user should be able to retrieve both credentials from the Bitwarden web vault and enter them into the respective prompts without the dialogs competing for focus. Either:
- Both fields presented in a single dialog, or
- A brief pause / user-triggered continuation between prompts, or
- Support for passing credentials via stdin or environment variables to allow scripted input
Actual behavior
Second dialog opens before the user can switch windows, forcing the user to have both values memorized or visible on screen simultaneously before starting the command.
Workaround
Use pinentry-curses instead of pinentry-gnome3. The curses dialog runs inline in the terminal and does not grab window focus, allowing free window switching between prompts.
Environment
- rbw 0.9.x
- Bitwarden cloud
- GNOME / Wayland (NixOS)
Problem
rbw registerprompts forclient_idandclient_secretvia two sequential pinentry dialogs. Withpinentry-gnome3, each dialog grabs focus and the next one opens immediately after the previous is dismissed. This makes it impossible to switch to another window to copy theclient_secretafter entering theclient_id.Steps to reproduce
pinentry-gnome3rbw registerclient_idin the first GNOME pinentry dialog and confirmclient_secret) opens immediatelyclient_secretExpected behavior
The user should be able to retrieve both credentials from the Bitwarden web vault and enter them into the respective prompts without the dialogs competing for focus. Either:
Actual behavior
Second dialog opens before the user can switch windows, forcing the user to have both values memorized or visible on screen simultaneously before starting the command.
Workaround
Use
pinentry-cursesinstead ofpinentry-gnome3. The curses dialog runs inline in the terminal and does not grab window focus, allowing free window switching between prompts.Environment