Package Details: bitwarden 1.25.1-2

Git Clone URL: https://aur.archlinux.org/bitwarden.git (read-only, click to copy)
Package Base: bitwarden
Description: Bitwarden Desktop Application
Upstream URL: https://github.com/bitwarden/desktop
Keywords: password-manager
Licenses: GPL3
Conflicts: bitwarden-bin, bitwarden-git
Submitter: libertylocked
Maintainer: libertylocked
Last Packager: libertylocked
Votes: 78
Popularity: 7.50
First Submitted: 2018-10-11 08:37
Last Updated: 2021-04-04 19:06

Pinned Comments

libertylocked commented on 2019-11-11 02:58

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

yochananmarqos commented on 2021-05-04 16:52

@Tha-Fox: Try my PKGBUILD using Node.js 12.

FYI, Node.js 10 was EOL as of April 30th.

Tha-Fox commented on 2021-05-04 06:12

I tried to install this, but got the following error:

3476 silly lifecycle @nodert-win10-rs4/windows.security.credentials.ui@0.4.4~install: Returned: code: 1 signal: null

3477 info lifecycle @nodert-win10-rs4/windows.security.credentials.ui@0.4.4~install: Failed to exec install script

<clip>

3483 verbose stack Error: @nodert-win10-rs4/windows.security.credentials.ui@0.4.4 install: node-gyp rebuild

3483 verbose stack Exit status 1

3483 verbose stack at EventEmitter.<anonymous> (/home/user/.nvm/versions/node/v10.24.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)

3483 verbose stack at EventEmitter.emit (events.js:198:13)

3483 verbose stack at ChildProcess.<anonymous> (/home/user/.nvm/versions/node/v10.24.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)

3483 verbose stack at ChildProcess.emit (events.js:198:13)

3483 verbose stack at maybeClose (internal/child_process.js:982:16)

3483 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)

3484 verbose pkgid @nodert-win10-rs4/windows.security.credentials.ui@0.4.4

3485 verbose cwd /home/user/.cache/aurman/bitwarden/src/desktop-1.25.1/build

3486 verbose Linux 5.11.16-arch1-1

3487 verbose argv "/home/user/.nvm/versions/node/v10.24.0/bin/node" "/home/user/.nvm/versions/node/v10.24.0/bin/npm" "install" "--production" "--cache-min" "999999999"

3488 verbose node v10.24.0

3489 verbose npm v6.14.11

3490 error code ELIFECYCLE

3491 error errno 1

3492 error @nodert-win10-rs4/windows.security.credentials.ui@0.4.4 install: node-gyp rebuild

3492 error Exit status 1

3493 error Failed at the @nodert-win10-rs4/windows.security.credentials.ui@0.4.4 install script.

3493 error This is probably not a problem with npm. There is likely additional logging output above.

3494 verbose exit [ 1, true ]

dottorblaster commented on 2021-04-03 17:48 

[22355:0403/194346.065382:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[22323:0403/194346.441079:INFO:CONSOLE(38700)] "Uncaught ReferenceError: require is not defined", source: file:///usr/lib/bitwarden/resources/app.asar/app/main.js (38700)

Looks like electron 12 breaks the package? Also, I tried to rebuild and it didn't help :/

Edit: it works with the latest release, thanks for the update!

gochkin commented on 2021-03-13 18:34

bitwarden has been updated to use electron 11. You can remove the electron9 dependency.

yochananmarqos commented on 2020-10-16 05:07

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

libertylocked commented on 2020-10-16 03:53

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.

tfjade commented on 2020-10-15 19:34

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.

totonebadass commented on 2020-10-15 13:29

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!

yochananmarqos commented on 2020-10-13 17:57

@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.

PedroHLC commented on 2020-10-13 13:45

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.