Linux beta: testing and feedback

[capkz]

BwPicker 1.1.0 is the first release with a Linux build. It's a beta: it has been tested in virtual machines, not yet on many real desktops. Please try it and report back here.

Download and install

From the 1.1.0 release, pick BwPicker-linux-x64.zip (most PCs) or BwPicker-linux-arm64.zip (ARM, e.g. Raspberry Pi 5), then:

unzip BwPicker-linux-x64.zip -d BwPicker && cd BwPicker
sh install-linux.sh

It installs to ~/.local/share/BwPicker (it updates itself from there), adds a menu entry and starts in the tray. If the Bitwarden CLI is missing, BwPicker offers to install the official one.

What to expect

• X11 (Xfce, MATE, Cinnamon, KDE or GNOME on Xorg): works like on Windows. Ctrl+Alt+B, ranked logins, typing with the usual safety checks, copying (needs xclip).
• Wayland (GNOME 46+, KDE Plasma 6, Hyprland): the desktop asks once to add the Ctrl+Alt+B shortcut and once to allow keyboard control. After that it types like on Windows, with two differences:
  • Only characters on your keyboard layout can be typed. A login with other characters (e.g. € or emoji on a US layout) is refused, so copy it instead.
  • If an app doesn't report itself to the accessibility bus, the picker says "unverified" before typing.
• Older Wayland desktops without the shortcut/keyboard portals: bind a shortcut to ~/.local/share/BwPicker/BwPicker --pick and copy with Ctrl+U / Ctrl+P (needs wl-clipboard).

Tested so far

• Ubuntu 24.04 + Xfce (X11): typing into GTK forms including Unicode and Caps Lock, copying, lock-screen clearing, the CLI installer, autostart.
• Ubuntu 26.04 + GNOME 50 (Wayland): the shortcut and permission prompts, typing into a GTK 4 form and into Discord's login, copying, lock-screen clearing.
• The ARM64 build has only been started under emulation, not on real ARM hardware yet.

Not tested yet: KDE Plasma, Hyprland/Sway, Fedora/Arch/openSUSE, real ARM devices, multi-monitor and HiDPI on Linux.

Reporting

Reply here with:

1. Distro and version, desktop, and X11 or Wayland (echo $XDG_SESSION_TYPE)
2. x64 or ARM64
3. The app you used it with and what happened (screenshots help; never post real usernames or passwords)

For a clear bug, an issue is fine too. Security problems go to a private security advisory, not here.