Linux Desktop Client blanks out when entering vault key #6560

KPS-MWT · 2023-10-12T09:44:13Z

Steps To Reproduce

Install Bitwarden 2023.9.1 or earlier through DEB package
generate vault with vault key
Update to 2023.9.2 through DEB package
Start Bitwarden
Try to enter vault

Expected Result

Vault key entered and vault unlocked

Actual Result

Bitwarden client blanks out completely. Can be restored by "view" -> "reload", but vault unlock try causes same result

Screenshots or Videos

Bildschirmaufzeichnung.vom.12.10.2023.11.39.17.webm

Additional Context

Uninstalling 2023.9.2 and reinstalling 2023.9.1 makes everything working ok again.

Output from Shell when Bitwarden is run from there:

(node:39123) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use bitwarden --trace-deprecation ... to show where the warning was created)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
(node:39123) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
at BiometricsService. (/opt/Bitwarden/resources/app.asar/main.js:47194:55)
at Generator.next ()
at /opt/Bitwarden/resources/app.asar/main.js:47160:71
at new Promise ()
at biometrics_service_awaiter (/opt/Bitwarden/resources/app.asar/main.js:47156:12)
at BiometricsService.init (/opt/Bitwarden/resources/app.asar/main.js:47193:16)
at Main. (/opt/Bitwarden/resources/app.asar/main.js:53805:46)
at Generator.next ()
at fulfilled (/opt/Bitwarden/resources/app.asar/main.js:53702:58)
(node:39123) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
11:42:59.090 › Error: No password found
11:42:59.143 › Error: No password found
11:42:59.193 › Error: No password found
11:42:59.194 › Error: No password found
11:42:59.194 › Error: No password found
11:42:59.240 › Error: No password found
11:42:59.275 › TypeError: Cannot read properties of undefined (reading 'osSupportsBiometric')
at BiometricsService. (/opt/Bitwarden/resources/app.asar/main.js:47199:55)
at Generator.next ()
at /opt/Bitwarden/resources/app.asar/main.js:47160:71
at new Promise ()
at biometrics_service_awaiter (/opt/Bitwarden/resources/app.asar/main.js:47156:12)
at BiometricsService.osSupportsBiometric (/opt/Bitwarden/resources/app.asar/main.js:47198:16)
at BiometricsService. (/opt/Bitwarden/resources/app.asar/main.js:47209:58)
at Generator.next ()
at fulfilled (/opt/Bitwarden/resources/app.asar/main.js:47157:58)
11:42:59.276 › TypeError: Cannot read properties of undefined (reading 'osSupportsBiometric')
at BiometricsService. (/opt/Bitwarden/resources/app.asar/main.js:47199:55)
at Generator.next ()
at /opt/Bitwarden/resources/app.asar/main.js:47160:71
at new Promise ()
at biometrics_service_awaiter (/opt/Bitwarden/resources/app.asar/main.js:47156:12)
at BiometricsService.osSupportsBiometric (/opt/Bitwarden/resources/app.asar/main.js:47198:16)
at DesktopCredentialStorageListener. (/opt/Bitwarden/resources/app.asar/main.js:47383:59)
at Generator.next ()
at /opt/Bitwarden/resources/app.asar/main.js:47311:71
at new Promise ()
11:42:59.277 › Error: No password found
11:43:00.186 › Error: No password found
[39123:1012/114301.905771:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
11:43:01.975 › Error: No password found
11:43:02.202 › Error: No password found
11:43:02.685 › Error: No password found
11:43:02.931 › Error: No password found
11:43:03.213 › Error: No password found
[39157:1012/114304.117925:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Operating System

Linux

Operating System Version

Ubuntu 22.04

Installation method

Direct Download (from bitwarden.com)

Build Version

Version 2023.9.2 Shell 26.3.0 Renderer 116.0.5845.228 Node 18.16.1 Architecture x64

Issue Tracking Info

I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

The text was updated successfully, but these errors were encountered:

jusevitch · 2023-10-12T16:17:58Z

I can confirm this on Ubuntu 20.04 for version 2023.9.2. When I start typing my master password in the field, the window blanks out. Menus are accessible, but the app itself is unusable.

jdhaines · 2023-10-12T16:58:39Z

I'm seeing this behavior, but user interaction doesn't seem to affect it. I can open the application and just wait 3-5 seconds to see the "crash". Menus are still clickable, but the central UI is just blank. If I keep my mouse cursor on the screen it seems to wait not exhibit the "crash" but one mouse-out and mouse-back kicks it off. The current AppImage seems to be 2023.8.2 and doesn't exhibit this behavior.

My error is similar to above:

Logs

(node:262630) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use `bitwarden --trace-deprecation ...` to show where the warning was created)
(node:262630) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
    at BiometricsService. (/opt/Bitwarden/resources/app.asar/main.js:47194:55)
    at Generator.next ()
    at /opt/Bitwarden/resources/app.asar/main.js:47160:71
    at new Promise ()
    at biometrics_service_awaiter (/opt/Bitwarden/resources/app.asar/main.js:47156:12)
    at BiometricsService.init (/opt/Bitwarden/resources/app.asar/main.js:47193:16)
    at Main. (/opt/Bitwarden/resources/app.asar/main.js:53805:46)
    at Generator.next ()
    at fulfilled (/opt/Bitwarden/resources/app.asar/main.js:53702:58)
(node:262630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
(node:262630) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading 'null')
    at new Menubar (/opt/Bitwarden/resources/app.asar/main.js:45540:131)
    at MenuMain. (/opt/Bitwarden/resources/app.asar/main.js:45594:56)
    at Generator.next ()
    at fulfilled (/opt/Bitwarden/resources/app.asar/main.js:45564:58)
(node:262630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

willmartian · 2023-10-12T21:06:03Z

Thanks for the bug report! I am able to reliably reproduce on Ubuntu 22.04.2 with both deb and AppImage. It looks like this might have been caused by our recent Electron update. The team is looking into a resolution now.

Potentially related: electron/electron#32760

LeeRoyManea · 2023-10-13T07:36:58Z

Same Issue on newest Fedora Beta

lukeab · 2023-10-13T09:02:15Z

Same issue on AppImage and flatpack installs on ubuntu 23.04, even just login screen when first setting up, enter email field shows for 3/5 seconds then blanks out, using the menu, view->reload shows it again for 3 to 5 seconds and blanks again

Command line Trace

luke@luke-strix-670e-f-7900x3d  ~/opt/Bitwarden  ./Bitwarden-2023.9.2-x86_64.AppImage
(node:64111) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use `bitwarden --trace-deprecation ...` to show where the warning was created)
(node:64111) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
    at BiometricsService.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47194:55)
    at Generator.next (<anonymous>)
    at /tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47160:71
    at new Promise (<anonymous>)
    at biometrics_service_awaiter (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47156:12)
    at BiometricsService.init (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47193:16)
    at Main.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:53805:46)
    at Generator.next (<anonymous>)
    at fulfilled (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:53702:58)
(node:64111) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:64111) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading 'null')
    at new Menubar (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45540:131)
    at MenuMain.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45594:56)
    at Generator.next (<anonymous>)
    at fulfilled (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45564:58)
(node:64111) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
10:01:00.528 › Checking for update
10:01:01.028 › Update for version 2023.9.2 is not available (latest version: 2023.9.2, downgrade is disallowed).

Findarato · 2023-10-13T17:32:02Z

What version should we be running as I am still getting this crash with the most recent published version?

abysso2 · 2023-10-13T17:39:22Z

What version should we be running as I am still getting this crash with the most recent published version?

2023.9.1 works like a charm

larouxn · 2023-10-13T23:42:19Z

What version should we be running as I am still getting this crash with the most recent published version?

2023.9.1 works like a charm

Indeed seems like an issue with 2023.9.2. As mentioned above, most likely related change is the Electron bump: #6511.

juliocesarpg92 · 2023-10-14T08:27:32Z

I installed the previous version as commented before, but now the window don't even open. I'm just getting this on the console.

(node:2) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use `bitwarden --trace-deprecation ...` to show where the warning was created)
Gtk-Message: 12:22:28.454: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:22:28.455: Failed to load module "canberra-gtk-module"

to update i used the next hash

flatpak update --commit=c78a73925d4c7bc6c4bf3c0139b4cc3ec44af20fdbfcc005320453b45a524366 com.bitwarden.desktop

also tried with the version 2022.8.4

atraxsrc · 2023-10-14T11:05:26Z

Same issue on Pop_os, using browser extention for now.

Edit: Password manager in the browser, is kinda sus, I went paranoid and install previous .deb version [https://github.com/bitwarden/clients/releases/download/desktop-v2023.8.4/Bitwarden-2023.8.4-amd64.deb], uninstalled latest flatpak, and no issues at all.

Jon-Kle · 2023-10-14T15:42:48Z

Same problem here on Fedora Linux 38 (Workstation Edition) with the flatpack version.
I upgraded to Version 2023.9.2 and now it crashes after a short period of time after starting it.

stephane-klein · 2023-10-14T19:23:49Z

Same issue here: https://discussion.fedoraproject.org/t/bitwarden-flatpak-crash-typeerror-cannot-read-properties-of-undefined-reading-ossupportsbiometric/92674

hal1961 · 2023-10-15T17:17:40Z

Meantime whenever Bitwarden-2023.9.1-x86_64.AppImage starts it automatically upgrades itself to the buggy Bitwarden-2023.9.2-x86_64.AppImage. I didn't find any setting to disable this behaviour. Also tried to set the file read only for everyone and changed the owner to root: even launched as normal user the file is replaced as well. Any hint to prevent the automatic update, at least until a fix is released?

pjgg · 2023-10-15T17:19:16Z

I can reproduce with Fedora 38

rogue5oul · 2023-10-15T19:31:23Z

I have the same behavior with flatpak version:
Version 2023.9.2
Shell 26.3.0
Renderer 116.0.5845.228
Node 18.16.1
Architecture x64

Running PopOS 22.04

Grizz69 · 2023-10-15T19:32:33Z

I have had problems using Blend OS and Fedora38 both installed via Flatpak. AppImage does the same thing. Recent since yesterday. I have uninstalled and reinstalled including different OS. Only thing that seems to work is the browser extension, and I hate browser extensions. Currently using Fedora Silverblue 38.

HandcartCactus · 2023-10-15T22:58:05Z

Same issue on a fresh install of Linux Mint 21.2 Cinnamon 5.8.4, for both the .appimage and the .deb; like above, I also saw the same error message in the command line, although they did happen before the page disappeared:

luke@luke-strix-670e-f-7900x3d  ~/opt/Bitwarden  ./Bitwarden-2023.9.2-x86_64.AppImage
(node:64111) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use `bitwarden --trace-deprecation ...` to show where the warning was created)
(node:64111) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
    at BiometricsService.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47194:55)
    at Generator.next (<anonymous>)
    at /tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47160:71
    at new Promise (<anonymous>)
    at biometrics_service_awaiter (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47156:12)
    at BiometricsService.init (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:47193:16)
    at Main.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:53805:46)
    at Generator.next (<anonymous>)
    at fulfilled (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:53702:58)
(node:64111) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:64111) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading 'null')
    at new Menubar (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45540:131)
    at MenuMain.<anonymous> (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45594:56)
    at Generator.next (<anonymous>)
    at fulfilled (/tmp/.mount_BitwarZFVBrF/resources/app.asar/main.js:45564:58)
(node:64111) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
10:01:00.528 › Checking for update
10:01:01.028 › Update for version 2023.9.2 is not available (latest version: 2023.9.2, downgrade is disallowed).

I looked into my journalctl and saw that there was actually a segfault and a core dump when the screen went white. I'm not sure how helpful this is, but here's the start of one of them:

bitwarden[16870]: segfault at 15a580001048 ip 0000564261c47f03 sp 00007ffe60b32450 error 27 in bitwarden[56425e2c5000+79cb000]
systemd-coredump[16925]: Process 16870 (bitwarden) of user 1000 dumped core.
                                                      Found module bitwarden with build-id: f5155371198e2958d1d28aa0316948e7e34b2dce
                                                      #0  0x0000564261c47f03 n/a (bitwarden + 0x58dcf03)
...

ricjuhnl · 2023-10-17T05:47:48Z

Same issue on Debian 12 bookworm with Flatpak version:

(node:2) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use bitwarden --trace-deprecation ... to show where the warning was created)
Gtk-Message: 07:44:47.991: Failed to load module "xapp-gtk3-module"
(node:2) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
    at BiometricsService.<anonymous> (/app/Bitwarden/resources/app.asar/main.js:47194:55)
    at Generator.next (<anonymous>)
    at /app/Bitwarden/resources/app.asar/main.js:47160:71
    at new Promise (<anonymous>)
    at biometrics_service_awaiter (/app/Bitwarden/resources/app.asar/main.js:47156:12)
    at BiometricsService.init (/app/Bitwarden/resources/app.asar/main.js:47193:16)
    at Main.<anonymous> (/app/Bitwarden/resources/app.asar/main.js:53805:46)
    at Generator.next (<anonymous>)
    at fulfilled (/app/Bitwarden/resources/app.asar/main.js:53702:58)
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:2) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading 'null')
    at new Menubar (/app/Bitwarden/resources/app.asar/main.js:45540:131)
    at MenuMain.<anonymous> (/app/Bitwarden/resources/app.asar/main.js:45594:56)
    at Generator.next (<anonymous>)
    at fulfilled (/app/Bitwarden/resources/app.asar/main.js:45564:58)
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at WebFrameMain.send (node:electron/js2c/browser_init:2:94576)
    at WebContents.send (node:electron/js2c/browser_init:2:79721)
    at BrowserWindow.<anonymous> (/app/Bitwarden/resources/app.asar/main.js:46672:38)
    at BrowserWindow.emit (node:events:525:35)```

jtaala · 2023-10-17T10:48:34Z

See same on Arch linux with latest version with:

flatpak
appimage

Reverted version to 2023.9.1 and chattr +i'd the appimage so it can't update...

buvinghausen · 2023-10-17T13:39:54Z

Pretty sure this is borked on every Linux distro via all distribution channels

abysso2 · 2023-10-17T13:58:53Z

Solved with new release 2023.9.3:

https://github.com/bitwarden/clients/releases

buvinghausen · 2023-10-17T14:09:05Z

Having the same issue on fedora 38 using flatpak. You can however downgrade to the previous version through flatpak using the steps used at https://itsfoss.com/downgrade-flatpak-packages/

I had to downgrade both com.bitwarden.desktop and com.bitwarden.desktop.Locale

Since flatpak is usually a delay from OG release this will downgrade to 2023.9.1 which will work in the meantime.

sudo flatpak update --commit=c78a73925d4c7bc6c4bf3c0139b4cc3ec44af20fdbfcc005320453b45a524366 com.bitwarden.desktop

sudo flatpak update --commit=5ccea7bae339082be13d8fc35584e98301cfe00b441207cff18d32ebfb13618d com.bitwarden.desktop.Locale

Update: 2023.9.3 made it to Flatpak so this workaround is no longer needed

sixerstyle · 2023-10-20T15:42:55Z

Solved with new release 2023.9.3:

https://github.com/bitwarden/clients/releases

Isnt fixed, same Problem on 2023.9.3:

unning '/usr/bin/bwrap --args 40 bitwarden --trace-deprecation'
(node:2) DeprecationWarning: file property is deprecated and will be removed in v5.
at new ElectronLogService (/app/Bitwarden/resources/app.asar/main.js:47508:50)
at new Main (/app/Bitwarden/resources/app.asar/main.js:53758:27)
at 64164 (/app/Bitwarden/resources/app.asar/main.js:44265:18)
at webpack_require (/app/Bitwarden/resources/app.asar/main.js:58132:42)
at /app/Bitwarden/resources/app.asar/main.js:58188:37
at Object. (/app/Bitwarden/resources/app.asar/main.js:58190:12)
at Module._compile (node:internal/modules/cjs/loader:1269:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1324:10)
at Module.load (node:internal/modules/cjs/loader:1124:32)
at Module._load (node:internal/modules/cjs/loader:965:12)
(node:2) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'init')
at BiometricsService. (/app/Bitwarden/resources/app.asar/main.js:47194:55)
at Generator.next ()
at /app/Bitwarden/resources/app.asar/main.js:47160:71
at new Promise ()
at biometrics_service_awaiter (/app/Bitwarden/resources/app.asar/main.js:47156:12)
at BiometricsService.init (/app/Bitwarden/resources/app.asar/main.js:47193:16)
at Main. (/app/Bitwarden/resources/app.asar/main.js:53805:46)
at Generator.next ()
at fulfilled (/app/Bitwarden/resources/app.asar/main.js:53702:58)
(Use bitwarden --trace-warnings ... to show where the warning was created)
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:2) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading 'null')
at new Menubar (/app/Bitwarden/resources/app.asar/main.js:45540:131)
at MenuMain. (/app/Bitwarden/resources/app.asar/main.js:45594:56)
at Generator.next ()
at fulfilled (/app/Bitwarden/resources/app.asar/main.js:45564:58)
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[41:1020/174057.588766:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[41:1020/174057.590011:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!

hevanaa · 2023-10-20T15:51:50Z

It works again in Fedora 38 with 2023.9.3 version from flathub.

But I still get this annoying message "We're sorry, it looks like Bitwarden crashed" message in Gnome every time Bitwarden is locked. If you start it from command line, it's full of error messages.

E.g. things like this:
› Error: No password found
(node:2) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu')
at TrayMain.updateContextMenu (/app/Bitwarden/resources/app.asar/main.js:46304:23)

(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)

sixerstyle · 2023-10-24T10:53:27Z

in Gnome its works with version 2023.9.3. In KDE not, same error there, blank after 2sek

offline4ever · 2023-11-02T21:39:37Z

@ricjuhnl @sgilissen @llabusch93

I am also on Debian 12 and have the latest Flatpak version installed (2023.10.0), deactivating graphics acceleration solved it for me.

flatpak override --nodevice=dri --user com.bitwarden.desktop

No solution for the problem, but at least a workaround.

flonix8 · 2023-11-04T11:40:58Z

I have a similar issue. Had the blanking issue, 2023.9.3 fixed it for me (on KDE 5.27), but now 2023.10.0 introduced a new issue, where the window goes blank except some very few elements. I can still see the cursor (and everything technically works, i.e. I can unlock the vault) but nothing else. Even devtools are mostly blank. So it's back to being unusable again.

@offline4ever Thank you so much for the workaround. It seems to work.

I'm getting more and more frustrated with the Bitwarden situation on Linux though...

buvinghausen · 2023-11-06T15:48:45Z

I'm getting more and more frustrated with the Bitwarden situation on Linux though...

Yeah if you hit .333 in baseball you are a first ballot hall of famer. When only 1/3rd of your releases work in software you need to find a new profession.

larouxn · 2023-11-07T03:52:32Z

EDIT: 2023.10.1 does not resolve the blank issue.

Looks like a fresh desktop client release is out. Let's see if it addresses the blank issue.

https://github.com/bitwarden/clients/releases/tag/desktop-v2023.10.1

gbcox · 2023-11-10T13:42:32Z

2023.10.0 was working fine for me with Fedora 39, but when I upgraded to 2023.10.1 I got the white screen.

Edit: I not sure what is going on but I had to go back to 2023.9.2 to get this working again. It appears to have something to do with login.

rqkeating · 2023-11-12T04:26:52Z

Kubuntu 23.10, flatpak 1.14.4-2, Bitwarden 2023.10.1

I was able to get Bitwarden working by turning off the "GPU acceleration" for that flatpak. I used Flatseal to make that change but I think there are other ways of setting flatpak permissions too.

Seems to only occur on some GPUs, e.g. some Intel GPUs. See also bitwarden/clients#6560. Cannot go back to electron 25 easily due to NixOS#272912.

Seems to only occur on some GPUs, e.g. some Intel GPUs. See also bitwarden/clients#6560. Cannot go back to electron 25 easily due to NixOS#272912. Since upstream has a commit to do this, backport it (it does not apply cleanly, though, so vendor).

Seems to only occur on some GPUs, e.g. some Intel GPUs. See also bitwarden/clients#6560. Cannot go back to electron 25 easily due to #272912. Since upstream has a commit to do this, backport it (it does not apply cleanly, though, so vendor). (cherry picked from commit 333dadb)

Seems to only occur on some GPUs, e.g. some Intel GPUs. See also bitwarden/clients#6560. Cannot go back to electron 25 easily due to NixOS#272912. Since upstream has a commit to do this, backport it (it does not apply cleanly, though, so vendor).

pogues · 2023-12-19T15:36:08Z

Still seeing the same behaviour on Fedora39 with Bitwarden 2023.12.0 via flatpak (i.e. crashes before I can enter the password)
Tried removing the "GPU acceleration" but that did not fix.
Interestingly the AppImage I just installed with the same version is working

sixerstyle · 2023-12-21T19:56:46Z

Still seeing the same behaviour on Fedora39 with Bitwarden 2023.12.0 via flatpak (i.e. crashes before I can enter the password) Tried removing the "GPU acceleration" but that did not fix. Interestingly the AppImage I just installed with the same version is working

I found the error in mine. after installation in fedora bitwarden didn't have background permission. try

sudo flatpak permission-set background background com.bitwarden.desktop

KPS-MWT added bug desktop Desktop Application labels Oct 12, 2023

willmartian self-assigned this Oct 12, 2023

willmartian mentioned this issue Oct 13, 2023

[PM-4300] downgrade Electron to v25.9.1 #6573

Merged

willmartian closed this as completed in #6573 Oct 13, 2023

This was referenced Oct 13, 2023

Client 2023.9.2 broken on Linux (Mint Cinnamon) #6577

Closed

Login View Disappears; Can't login on Linux. #6578

Closed

djsmith85 mentioned this issue Oct 13, 2023

Bitwarden login page disappears (Debian..not sure of other systems) #6580

Closed

1 task

trmartin4 reopened this Oct 13, 2023

cmdcolin mentioned this issue Oct 13, 2023

Jbrowse 2.7.0 crash GMOD/jbrowse-components#3979

Closed

This was referenced Oct 15, 2023

Bitwarden on Linux Mint - sign in page disappears and the window goes blank. #6584

Closed

bitwarden: 2023.9.0 -> 2023.9.3 NixOS/nixpkgs#260699

Closed

djsmith85 mentioned this issue Oct 15, 2023

Flatpak from official default repository and AppImage from Bitwarden website blank after 2-5 seconds (sign-in page, no info on other page as it's stuck on the sign in one) #6587

Closed

1 task

sammbw mentioned this issue Oct 16, 2023

Login Screen loads then crashes #6599

Closed

1 task

djsmith85 mentioned this issue Oct 17, 2023

2023.9.2 AppImage fails to open tresor on Debian 12.2 #6603

Closed

1 task

djsmith85 mentioned this issue Oct 18, 2023

Box for Master Password disappears after short time #6618

Closed

1 task

djsmith85 closed this as completed Oct 18, 2023

noelmiller mentioned this issue Oct 18, 2023

Upgrade Flatpak to 2023.9.3 flathub/com.bitwarden.desktop#162

Closed

djsmith85 mentioned this issue Oct 18, 2023

bitwarden desktop linux starts white screen and unresponsive #5628

Closed

1 task

djsmith85 mentioned this issue Oct 23, 2023

App turns blank after 2 sec #6666

Closed

1 task

sammbw mentioned this issue Oct 26, 2023

Loading screen when starting does not go to access #6704

Closed

1 task

SuperSandro2000 mentioned this issue Dec 7, 2023

Revert "electron_25: eol" NixOS/nixpkgs#272658

Closed

13 tasks

amarshall added a commit to amarshall/nixpkgs that referenced this issue Dec 13, 2023

bitwarden: use Electron 27 instead of 26 to fix bug

0b9d173

Seems to only occur on some GPUs, e.g. some Intel GPUs. See also bitwarden/clients#6560. Cannot go back to electron 25 easily due to NixOS#272912.

amarshall mentioned this issue Dec 13, 2023

bitwarden: use Electron 27 instead of 26 to fix bug NixOS/nixpkgs#273861

Merged

13 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Linux Desktop Client blanks out when entering vault key #6560

Linux Desktop Client blanks out when entering vault key #6560

KPS-MWT commented Oct 12, 2023

jusevitch commented Oct 12, 2023

jdhaines commented Oct 12, 2023

willmartian commented Oct 12, 2023 •

edited

LeeRoyManea commented Oct 13, 2023

lukeab commented Oct 13, 2023

Findarato commented Oct 13, 2023

abysso2 commented Oct 13, 2023

larouxn commented Oct 13, 2023

juliocesarpg92 commented Oct 14, 2023 •

edited

atraxsrc commented Oct 14, 2023 •

edited

Jon-Kle commented Oct 14, 2023

stephane-klein commented Oct 14, 2023

hal1961 commented Oct 15, 2023 •

edited

pjgg commented Oct 15, 2023

rogue5oul commented Oct 15, 2023

Grizz69 commented Oct 15, 2023

HandcartCactus commented Oct 15, 2023

ricjuhnl commented Oct 17, 2023 •

edited

jtaala commented Oct 17, 2023

buvinghausen commented Oct 17, 2023

abysso2 commented Oct 17, 2023

buvinghausen commented Oct 17, 2023 •

edited

sixerstyle commented Oct 20, 2023

hevanaa commented Oct 20, 2023

sixerstyle commented Oct 24, 2023 •

edited

offline4ever commented Nov 2, 2023 •

edited

flonix8 commented Nov 4, 2023

buvinghausen commented Nov 6, 2023

larouxn commented Nov 7, 2023 •

edited

gbcox commented Nov 10, 2023 •

edited

rqkeating commented Nov 12, 2023

pogues commented Dec 19, 2023

sixerstyle commented Dec 21, 2023

Linux Desktop Client blanks out when entering vault key #6560

Linux Desktop Client blanks out when entering vault key #6560

Comments

KPS-MWT commented Oct 12, 2023

Steps To Reproduce

Expected Result

Actual Result

Screenshots or Videos

Additional Context

Operating System

Operating System Version

Installation method

Build Version

Issue Tracking Info

jusevitch commented Oct 12, 2023

jdhaines commented Oct 12, 2023

willmartian commented Oct 12, 2023 • edited

LeeRoyManea commented Oct 13, 2023

lukeab commented Oct 13, 2023

Findarato commented Oct 13, 2023

abysso2 commented Oct 13, 2023

larouxn commented Oct 13, 2023

juliocesarpg92 commented Oct 14, 2023 • edited

atraxsrc commented Oct 14, 2023 • edited

Jon-Kle commented Oct 14, 2023

stephane-klein commented Oct 14, 2023

hal1961 commented Oct 15, 2023 • edited

pjgg commented Oct 15, 2023

rogue5oul commented Oct 15, 2023

Grizz69 commented Oct 15, 2023

HandcartCactus commented Oct 15, 2023

ricjuhnl commented Oct 17, 2023 • edited

jtaala commented Oct 17, 2023

buvinghausen commented Oct 17, 2023

abysso2 commented Oct 17, 2023

buvinghausen commented Oct 17, 2023 • edited

sixerstyle commented Oct 20, 2023

hevanaa commented Oct 20, 2023

sixerstyle commented Oct 24, 2023 • edited

offline4ever commented Nov 2, 2023 • edited

flonix8 commented Nov 4, 2023

buvinghausen commented Nov 6, 2023

larouxn commented Nov 7, 2023 • edited

gbcox commented Nov 10, 2023 • edited

rqkeating commented Nov 12, 2023

pogues commented Dec 19, 2023

sixerstyle commented Dec 21, 2023

willmartian commented Oct 12, 2023 •

edited

juliocesarpg92 commented Oct 14, 2023 •

edited

atraxsrc commented Oct 14, 2023 •

edited

hal1961 commented Oct 15, 2023 •

edited

ricjuhnl commented Oct 17, 2023 •

edited

buvinghausen commented Oct 17, 2023 •

edited

sixerstyle commented Oct 24, 2023 •

edited

offline4ever commented Nov 2, 2023 •

edited

larouxn commented Nov 7, 2023 •

edited

gbcox commented Nov 10, 2023 •

edited