Arch Linux User Repository

@nemonein @windy I had the same problem with this version. But I updated my Vaultwarden server to version 1.37 and everything worked as before.

@windy Yeah, I've heard that. I'm the one who uses Vaultwarden. They know what's going on, so there maybe a fixed(stable) version soon.

@nemonein: Works as expected for me with KDE Plasma. The issue seems to be related when Vaultwarden is used as a backend instead of the default Bitwarden instance.

Hello. I've just installed 7.0 on my KDE plasma system. After I run, it does not display any contents of my vault, or I could not click any of items. Login, Cards, etc. However, Send, Generator, and other stuff work.

How about you guys?

@windy: The desktop file is launching the same binary with the included wrapper script. See bitwarden.sh.

A Bitwarden employee pointed out that this package is incorrectly calling the binary:

desktop-file-edit --set-key=Exec --set-value="${pkgname%-bin} %U" \
 "$pkgdir/usr/share/applications/${pkgname%-bin}.desktop"

Also it "fails to enable memory protections, possibly leaving your desktop app open to memory-dumping."

==> Starting package()... Error on file "/var/tmp/pamac-build-corey/bitwarden-bin/pkg/bitwarden-bin/usr/share/applications/bitwarden.desktop": No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

There's a mismatch between the post install note in bitwarden.install and the bitwarden.sh custom launch script.

The note in bitwarden.install states:

post_install() {
  note "Custom flags should be put directly in: ~/.config/bitwarden.conf"
}

However, the bitwarden.sh custom launch script reads:

# Allow users to override command-line options
if [[ -f "$XDG_CONFIG_HOME/bitwarden-flags.conf" ]]; then
   BITWARDEN_USER_FLAGS="$(grep -v '^#' "$XDG_CONFIG_HOME/bitwarden-flags.conf")"
fi

I propose the note in bitwarden.install to be updated to reflect what the launch script actually does and to keep it in line with other packages that do something similar, e.g. visual-studio-code-bin, chromium, google-chrome, microsoft-edge-stable-bin etc.

@zeroz: That is neither an issue with this package nor any other. Please see Disable debug packages and LTO. Only use the debug flag manually when you actually need to debug something.