Arch Linux User Repository

If the package breaks after electron update, rebuilding bitwarden should fix it. (Unless there is a way to trigger an auto rebuild whenever electron is upgraded?)

Whenever that happens feel free to leave a comment and I'll update the pkgrel

FYI, it builds and runs fine with electron9 9.3.2 and Node.js LTS Erbium (12.19.0).

For now I've updated the PKGBUILD to use electron6 (instead of latest electron) since that's the version official binaries are built. Hopefully it will reduce the frequency of breakages.

Thanks everyone for reporting the issues.

The latest Electron update to 10.1.3 seems to break Bitwarden, and rebuilding Bitwarden does not help. I downgraded electron to version 9.2.1, rebuilt Bitwarden, and now it starts normally again.

What I did was:

sudo downgrade electron

I selected version 9.2.1, which was number 74, and I chose to add the IgnorePkg for electron. The downgrade script can be found in the AUR.

Next, I rebuilt bitwarden:

yay -S bitwarden --rebuild

Bitwarden is working again.

Update: I submitted an issue with bitwarden-dekstop dev (https://github.com/bitwarden/desktop/issues/572), looks like same issue happens on MacOS as well.
The app starts for me but it just hangs at the loading animation.
This is what I get with the "--enable-logging" command line parameter:

[octavian@lenovo ~]$ bitwarden-desktop --enable-logging   
[6849:1015/140922.715279:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.  
[6817:1015/140922.995564:INFO:CONSOLE(31797)] "Uncaught TypeError: Cannot read property 'app' of undefined", source: file:///usr/lib/bitwarden/resources/app.asar/app/main.js (31797)  
 [6817:1015/140923.031337:INFO:CONSOLE(15)] "(electron) Security Warning: webFrame.executeJavaScript was called without worldSafeExecuteJavaScript enabled. This is considered unsafe. worldSafeExecuteJavaScript will be enabled by default in Electron 12.", source: electron/js2c/renderer_init.js (15)

Bitwarden about info:

Version 1.22.2  
Shell 10.1.3  
Renderer 85.0.4183.121  
Node 12.16.3  
Architecture x64

Help!

@PedroHLC: electron depends on libxss, it's already satisfied.

I don't see that pkg-config warning using my PKGBUILD with Node.js 12.

EDIT: I'm seeing that error now, but it's apparently due to Electron 10.

New dep libxss, otherwise it fails in a clean chroot with:

Package xscrnsaver was not found in the pkg-config search path.
Perhaps you should add the directory containing `xscrnsaver.pc'

Also, now it requires an xorg running to build, so it's probably better to wrap it in xvfb. For that add xorg-server-xvfb to makedepends, and prepend xvfb-run -a -n 97 to npm run build.

NODE_MODULE_VERSION 80. This version of Node.js requires NODE_MODULE_VERSION 82. Please try re-compiling or re-installing

I already re-built bitwarden but no help

Official builds are built with node 10 too... We use the same version since CI runs on node 10, otherwise we'd be building using essentially an untested version. Maybe open a bug on their GitHub and ask them to build with node 12? (But again, we're using an untested version of electron, so maybe we can build with whatever node we want)

@libertylocked: Exactly. So why keep using an old, depreciated, insecure version of Node.js Dubnium instead of the latest? Why not use the latest Erbium?

The node version shown in Help > About is the node that's bundled in electron.

Because the official builds use electron-builder, at the time of writing it's using electron 6.1.7, which we can check, the node version is 12.4.0.

We use the latest electron in this PKGBUILD so it would be a newer version of node too.