Error when syncing the vault on Linux desktop

[zagota]

Steps To Reproduce

1. Go to 'File'
2. Click on 'sync vault'
3. Error sync vault

Expected Result

sync vault

Actual Result

Error sync vault

Screenshots or Videos

No response

Additional Context

I have installed version 2024.3.2 and can no longer synchronize the vault. I revert to 2024.3.0 and it works. Server is self hosted.

Operating System

Linux

Operating System Version

Ubuntu 22.04 LTS

Installation method

Snap

Build Version

"About Bitwarden" The application crashes

Issue Tracking Info

• [X] 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.

[ahmedmoktaar]

I had the same issue, but it worked fine if you installed version 2024.3.2 from the .deb file.

[PeterDrake]

Same issue, Ubuntu 22.04.4 LTS.

Also, when I try to save a new entry, I get an error "Failed to decode access token; JWT must have 3 parts".

[justin-yan]

Echo-ing everyone else - 2024.3.2 snap install presented issues in multiple ways:

• saved TOTP tokens no longer displayed generated codes (said "Premium plan required")
• attempts to sync or add items resulted in the "JWT must have 3 parts" banner error
• a complete log-out and then log-in resulted in a spinner and no items appearing

Reverting to 2024.3.0 restored functionality

[pescepilota]

Same issue Ubuntu 22.04.4 LTS

[marcosguedes]

I use snap and reverting versions worked (tip by @justin-yan ). Full command: sudo snap revert bitwarden

[jlf0dev]

Hi everyone, thank you for the reports! We moved to storing our tokens in secure storage with this release, but unfortunately snap packages are sandboxed and we can't automatically enable access to the password-manager-service permission. If you're running into this issue there are a couple fixes:

1. Ubuntu Software > Installed > Bitwarden > Permissions - turn on "Read, add, change or remove saved passwords"
2. Run the following: sudo snap connect bitwarden:password-manager-service

Please be sure to log out and back in after enabling this permission. If you encounter any issues please feel free to reach out, thanks!

[bacchilu]

Hi everyone, thank you for the reports! We moved to storing our tokens in secure storage with this release, but unfortunately snap packages are sandboxed and we can't automatically enable access to the password-manager-service permission. If you're running into this issue there are a couple fixes:

1. Ubuntu Software > Installed > Bitwarden > Permissions - turn on "Read, add, change or remove saved passwords"
2. Run the following: sudo snap connect bitwarden:password-manager-service

Please be sure to log out and back in after enabling this permission. If you encounter any issues please feel free to reach out, thanks!

Same problem on Ubuntu 23.10 Desktop and Bitwarden installed via snap package (current Bitwarden version: 2024.4.0).

Versione 2024.4.0
Shell 28.2.8
Renderer 120.0.6099.291
Node 18.18.2
Architecture x64

Unfortunately the described solution doesn't seem to work...

[pescepilota]

Hi everyone, thank you for the reports! We moved to storing our tokens in secure storage with this release, but unfortunately snap packages are sandboxed and we can't automatically enable access to the password-manager-service permission. If you're running into this issue there are a couple fixes:

1. Ubuntu Software > Installed > Bitwarden > Permissions - turn on "Read, add, change or remove saved passwords"
2. Run the following: sudo snap connect bitwarden:password-manager-service

Please be sure to log out and back in after enabling this permission. If you encounter any issues please feel free to reach out, thanks!

Same problem on Ubuntu 23.10 Desktop and Bitwarden installed via snap package (current Bitwarden version: 2024.4.0).

Versione 2024.4.0
Shell 28.2.8
Renderer 120.0.6099.291
Node 18.18.2
Architecture x64

Unfortunately the described solution doesn't seem to work...

Try logging out of your account (File > Esci > tuo account) and then logging back in. It worked for me

[CookieCr2nk]

I think i have the same issue, i installed "bitwarden" on ubuntu via snap. I have version stable 2024.4.0

Error: 0:12:04.375 › Error: Failed to decode access token: JWT must have 3 parts (node:27511) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu') at TrayMain.updateContextMenu (/snap/bitwarden/108/resources/app.asar/main.js:88410:23) at MessagingMain.updateTrayMenu (/snap/bitwarden/108/resources/app.asar/main.js:87873:28) at MessagingMain.onMessage (/snap/bitwarden/108/resources/app.asar/main.js:87795:22) at MessagingMain.<anonymous> (/snap/bitwarden/108/resources/app.asar/main.js:87783:155) at Generator.next (<anonymous>) at /snap/bitwarden/108/resources/app.asar/main.js:87760:71 at new Promise (<anonymous>) at messaging_main_awaiter (/snap/bitwarden/108/resources/app.asar/main.js:87756:12) at IpcMainImpl.<anonymous> (/snap/bitwarden/108/resources/app.asar/main.js:87783:83) at IpcMainImpl.emit (node:events:517:28) (node:27511) 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) ** Message: 20:12:11.557: Remote error from secret service: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.406" (uid=1000 pid=27511 comm="/snap/bitwarden/108/bitwarden --no-sandbox" label="snap.bitwarden.bitwarden (enforce)") interface="org.freedesktop.Secret.Service" member="OpenSession" error name="(unset)" requested_reply="0" destination=":1.7" (uid=1000 pid=2942 comm="/usr/bin/gnome-keyring-daemon --foreground --compo" label="unconfined")

[sean-abercrombie]

My bug report was marked as closed and pointed towards here as the same issue. But I am not on a Linux platform so the fix doesn't apply to me, I am on Windows. Newest version 2024.4.0 does not resolve the issue. Still have to downgrade to below 2024.3.2 to restore functionality.

[janvkn]

I'm still experiencing this issue with the Arch Linux package. I had to rollback to 2024.3.0 and remove my ~/.config/Bitwarden directory to get it to work.

Bitwarden is not a snap package on Arch Linux, so the snap connect ... workaround is not applicable.

Edit: I wanted to add that I managed to resolve my immediate issue by enabling kwallet, which I normally have disabled. So it seems that bitwarden-desktop now depends on a desktop environment's own password manager (i.e. kwallet, gnome-keyring, ...) This seems... illogical? It also means you can't even open your vault if you're running a more barebones window manager, not everyone chooses to run a full DE ...

[JohnTocher]

Hi everyone, thank you for the reports! We moved to storing our tokens in secure storage with this release, but unfortunately snap packages are sandboxed and we can't automatically enable access to the password-manager-service permission. If you're running into this issue there are a couple fixes:

1. Ubuntu Software > Installed > Bitwarden > Permissions - turn on "Read, add, change or remove saved passwords"
2. Run the following: sudo snap connect bitwarden:password-manager-service

Please be sure to log out and back in after enabling this permission. If you encounter any issues please feel free to reach out, thanks!

Same problem on Ubuntu 23.10 Desktop and Bitwarden installed via snap package (current Bitwarden version: 2024.4.0).

Versione 2024.4.0
Shell 28.2.8
Renderer 120.0.6099.291
Node 18.18.2
Architecture x64

Unfortunately the described solution doesn't seem to work...

Try logging out of your account (File > Esci > tuo account) and then logging back in. It worked for me

This didn't work for me, even after a full reboot I get the same error. In the end I uninstalled the snap and reinstalled from the .deb file I appreciate this means no automatic updates, but for now I'll take that over an update that might break things with no notice. System is: Ubuntu 23.10 64 bit GNOME 45.2, Wayland WS

[shorawitz]

I too am seeing this issue and not using snap (I think when I first started w/Birwarden, snap wasn't available): Ubuntu 23.10 KDE Bitwarden-2024.4.1-x86_64.AppImage

[jlf0dev]

Hey ya'll, this turned out to be a little bigger than we initially thought. We're working on a fix in #8776 that should resolve the token errors being reported.

If anyone has the time to test #8776 on their system, we would also appreciate the help. We're looking to discover potential issues early on. Thanks!

[TapGhoul]

Worth a note @jlf0dev - I have a secret service installed (kwallet) with the same issue. But it seems the problem isn't that bitwarden can't find it. The problem seems to be it fails to open the wallet! When I reboot, sync fails, as to be expected. However, if I open the wallet manually via kwalletmanager, all sync operations start to work!

[kaarelen]

bitwarden 2024.4.0-1 Arch Linux (rolling release, fully updated) without DE, barebone WM

01:00:41.323 › Error: Failed to decode access token: JWT must have 3 parts 01:00:41.323 › Received API exception: Error: Failed to decode access token: JWT must have 3 parts

on attempt to save new entry

I think it could be really better to make logs more informative. Application failed to do something with token (get it) because it (app) lacks permissions/dependencies/etc. It has to be in logs, because at this point logs are basically wrong, it's not decoding error. What do you think, @jlf0dev?

@janvkn so there is any normal workaround without roll backing? I really do not want to depend on some random desktop environment.

[tg-mw]

I had the same issue on Kubuntu 22.04.4 LTS (KDE). The fix mentioned above did not work for me until I installed gnome-keyring. It seems as if older versions of kwallet do not support the org.freedesktop.secrets DBus API, which seems to be necessary for Bitwarden to work properly.

[tabascosw]

I can confirm tg-mw comments. I use openSUSE Tumbleweed latest snapshot, installation of gnome-keyring made the appimage 2024-4.1 working again.

[shorawitz]

I have gnome-keyring: 42.1 installed on kubuntu 23.10. I can open Bitwarden-2024.4.1-x86_64.AppImage and view, but I try to edit an entry I get the error:

Received API exception: Error: Failed to decode access token: JWT must have 3 parts

[tabascosw]

I just played around a bit, de-installed gnome-keyring and installed the latest kwallet 6.1 (incl. pam-kwallet 6.04) and that also works, I can also edit entries.

[shorawitz]

:-( Kwallet 6.1 is the latest in Github. I won't see that in any Ubuntu distro I'll bet until next year (if I'm lucky.) I'll have to figure something else out until it's fixed

[FraioVeio]

Same problem here on Arch.

~ $ bitwarden-desktop
15:26:26.424 › State version: 48
15:26:26.428 › Migrator MinVersionMigrator (to version 3) should migrate: false - up
15:26:26.428 › Migrator RemoveEverBeenUnlockedMigrator (to version 4) should migrate: false - up
15:26:26.429 › Migrator AddKeyTypeToOrgKeysMigrator (to version 5) should migrate: false - up
15:26:26.429 › Migrator RemoveLegacyEtmKeyMigrator (to version 6) should migrate: false - up
15:26:26.429 › Migrator MoveBiometricAutoPromptToAccount (to version 7) should migrate: false - up
15:26:26.430 › Migrator MoveStateVersionMigrator (to version 8) should migrate: false - up
15:26:26.430 › Migrator MoveBrowserSettingsToGlobal (to version 9) should migrate: false - up
15:26:26.430 › Migrator EverHadUserKeyMigrator (to version 10) should migrate: false - up
15:26:26.431 › Migrator OrganizationKeyMigrator (to version 11) should migrate: false - up
15:26:26.431 › Migrator MoveEnvironmentStateToProviders (to version 12) should migrate: false - up
15:26:26.432 › Migrator ProviderKeyMigrator (to version 13) should migrate: false - up
15:26:26.432 › Migrator MoveBiometricClientKeyHalfToStateProviders (to version 14) should migrate: false - up
15:26:26.432 › Migrator FolderMigrator (to version 15) should migrate: false - up
15:26:26.432 › Migrator LastSyncMigrator (to version 16) should migrate: false - up
15:26:26.432 › Migrator EnablePasskeysMigrator (to version 17) should migrate: false - up
15:26:26.433 › Migrator AutofillSettingsKeyMigrator (to version 18) should migrate: false - up
15:26:26.433 › Migrator RequirePasswordOnStartMigrator (to version 19) should migrate: false - up
15:26:26.433 › Migrator PrivateKeyMigrator (to version 20) should migrate: false - up
15:26:26.433 › Migrator CollectionMigrator (to version 21) should migrate: false - up
15:26:26.433 › Migrator CollapsedGroupingsMigrator (to version 22) should migrate: false - up
15:26:26.433 › Migrator MoveBiometricPromptsToStateProviders (to version 23) should migrate: false - up
15:26:26.433 › Migrator SmOnboardingTasksMigrator (to version 24) should migrate: false - up
15:26:26.434 › Migrator ClearClipboardDelayMigrator (to version 25) should migrate: false - up
15:26:26.434 › Migrator RevertLastSyncMigrator (to version 26) should migrate: false - up
15:26:26.434 › Migrator BadgeSettingsMigrator (to version 27) should migrate: false - up
15:26:26.434 › Migrator MoveBiometricUnlockToStateProviders (to version 28) should migrate: false - up
15:26:26.434 › Migrator UserNotificationSettingsKeyMigrator (to version 29) should migrate: false - up
15:26:26.434 › Migrator PolicyMigrator (to version 30) should migrate: false - up
15:26:26.434 › Migrator EnableContextMenuMigrator (to version 31) should migrate: false - up
15:26:26.434 › Migrator PreferredLanguageMigrator (to version 32) should migrate: false - up
15:26:26.435 › Migrator AppIdMigrator (to version 33) should migrate: false - up
15:26:26.435 › Migrator DomainSettingsMigrator (to version 34) should migrate: false - up
15:26:26.435 › Migrator MoveThemeToStateProviderMigrator (to version 35) should migrate: false - up
15:26:26.435 › Migrator VaultSettingsKeyMigrator (to version 36) should migrate: false - up
15:26:26.435 › Migrator AvatarColorMigrator (to version 37) should migrate: false - up
15:26:26.435 › Migrator TokenServiceStateProviderMigrator (to version 38) should migrate: false - up
15:26:26.435 › Migrator MoveBillingAccountProfileMigrator (to version 39) should migrate: false - up
15:26:26.435 › Migrator OrganizationMigrator (to version 40) should migrate: false - up
15:26:26.436 › Migrator EventCollectionMigrator (to version 41) should migrate: false - up
15:26:26.436 › Migrator EnableFaviconMigrator (to version 42) should migrate: false - up
15:26:26.436 › Migrator AutoConfirmFingerPrintsMigrator (to version 43) should migrate: false - up
15:26:26.436 › Migrator UserDecryptionOptionsMigrator (to version 44) should migrate: false - up
15:26:26.436 › Migrator MergeEnvironmentState (to version 45) should migrate: false - up
15:26:26.436 › Migrator DeleteBiometricPromptCancelledData (to version 46) should migrate: false - up
15:26:26.436 › Migrator MoveDesktopSettingsMigrator (to version 47) should migrate: false - up
15:26:26.437 › Migrator MoveDdgToStateProviderMigrator (to version 48) should migrate: false - up
15:26:27.281 › State version: 48
15:26:27.290 › Error: The name is not activatable
15:26:27.294 › Error: The name is not activatable
15:26:27.299 › Error: The name is not activatable
15:26:27.303 › Error: The name is not activatable
15:26:27.311 › Error: The name is not activatable
15:26:27.312 › Error: The name is not activatable
15:26:27.340 › Error: The name is not activatable
15:26:27.341 › Error: The name is not activatable
15:26:27.351 › Error: The name is not activatable
15:26:27.379 › Error: The name is not activatable
15:26:27.379 › Error: The name is not activatable
15:26:27.380 › Error: The name is not activatable
15:26:27.394 › Error: The name is not activatable
15:26:27.395 › Error: The name is not activatable
15:26:27.400 › Error: The name is not activatable
15:26:27.407 › Error: The name is not activatable
15:26:27.407 › Error: The name is not activatable
15:26:27.408 › Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts
15:26:27.410 › Error: The name is not activatable
15:26:27.422 › Error: The name is not activatable
15:26:27.459 › Error: The name is not activatable
15:26:28.381 › Error: The name is not activatable
15:26:28.398 › Error: The name is not activatable
15:26:28.413 › Error: The name is not activatable

[android10]

I was also having the same issue:

• OS: Arch Linux
• Bitwarden desktop version: bitwarden 2024.4.0-1
• Backend: self-hosted
• Logs:

22:16:25.680 › Error: The name is not activatable
22:16:25.759 › Error: The name is not activatable
22:16:25.762 › Error: The name is not activatable
22:16:25.764 › Error: The name is not activatable
22:16:25.766 › Error: The name is not activatable
22:16:25.774 › Received API exception: Error: Failed to decode access token: JWT must have 3 parts
22:16:25.776 › Error: The name is not activatable
22:16:25.778 › Error: The name is not activatable
22:16:25.797 › Error: The name is not activatable
22:16:25.810 › Error: The name is not activatable
22:16:25.813 › Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts
22:16:27.815 › Error: The name is not activatable
22:16:27.822 › Error: The name is not activatable
22:16:37.818 › Error: The name is not activatable
22:16:37.827 › Error: The name is not activatable
22:16:47.817 › Error: The name is not activatable
22:16:47.826 › Error: The name is not activatable
22:16:57.817 › Error: The name is not activatable
22:16:57.826 › Error: The name is not activatable
22:17:07.818 › Error: The name is not activatable
22:17:07.827 › Error: The name is not activatable

Unfortunately none of the proposed solutions here worked for me, so there is anything else we can do other than rolling back to an older version and clean up the Bitwarden Desktop Client Cache and Settings:

1. sudo pacman -Rns bitwarden
2. rm -rf ~/.config/Bitwarden
3. ls /var/cache/pacman/pkg/bitwarden*
4. sudo pacman -U /var/cache/pacman/pkg/bitwarden-2024.3.0-1-x86_64.pkg.tar.zst (install any other older version)
5. Wait for a fix in my case since I do not know the codebase :(

I hope that helps.

Issues happen and be always grateful with the teams, contributors or anyone involved in any open source project.

Thanks for such a great project in any case! ❤️

[1nv1zzz]

I've also faced the same issue. Fixed it by cleaning the cache and running Bitwarden with the parameter --password-store=kwallet (I'm using arch+KDE). For Gnome users needed parameter looks like this: --password-store=gnome-libsecret I don't know the root cause of this issue, seems like something related to credentials storage because I've fixed the same issue with the Wire desktop application.

[ruanpereira]

OS: Arch Linux WM: bspwm DE: KDE Bitwarden desktop version: bitwarden 2024.4.0-1

I also have installed KDE DE on my system, the solution proposed above, using the parameter --password-store not works with me. Also confirmed that the Kwallet wallet is open, so i don't know for sure what is happening here. It is quite sad that RN is not working with Window Managers, hope the logs can get any clue to solve the problem.

• Logs:

bitwarden-desktop --password-store=kwallet
15:37:28.468 › State version: 48
15:37:28.475 › Migrator MinVersionMigrator (to version 3) should migrate: false - up
15:37:28.475 › Migrator RemoveEverBeenUnlockedMigrator (to version 4) should migrate: false - up
15:37:28.476 › Migrator AddKeyTypeToOrgKeysMigrator (to version 5) should migrate: false - up
15:37:28.476 › Migrator RemoveLegacyEtmKeyMigrator (to version 6) should migrate: false - up
15:37:28.477 › Migrator MoveBiometricAutoPromptToAccount (to version 7) should migrate: false - up
15:37:28.477 › Migrator MoveStateVersionMigrator (to version 8) should migrate: false - up
15:37:28.477 › Migrator MoveBrowserSettingsToGlobal (to version 9) should migrate: false - up
15:37:28.478 › Migrator EverHadUserKeyMigrator (to version 10) should migrate: false - up
15:37:28.478 › Migrator OrganizationKeyMigrator (to version 11) should migrate: false - up
15:37:28.479 › Migrator MoveEnvironmentStateToProviders (to version 12) should migrate: false - up
15:37:28.479 › Migrator ProviderKeyMigrator (to version 13) should migrate: false - up
15:37:28.479 › Migrator MoveBiometricClientKeyHalfToStateProviders (to version 14) should migrate: false - up
15:37:28.479 › Migrator FolderMigrator (to version 15) should migrate: false - up
15:37:28.479 › Migrator LastSyncMigrator (to version 16) should migrate: false - up
15:37:28.480 › Migrator EnablePasskeysMigrator (to version 17) should migrate: false - up
15:37:28.480 › Migrator AutofillSettingsKeyMigrator (to version 18) should migrate: false - up
15:37:28.480 › Migrator RequirePasswordOnStartMigrator (to version 19) should migrate: false - up
15:37:28.480 › Migrator PrivateKeyMigrator (to version 20) should migrate: false - up
15:37:28.480 › Migrator CollectionMigrator (to version 21) should migrate: false - up
15:37:28.480 › Migrator CollapsedGroupingsMigrator (to version 22) should migrate: false - up
15:37:28.481 › Migrator MoveBiometricPromptsToStateProviders (to version 23) should migrate: false - up
15:37:28.481 › Migrator SmOnboardingTasksMigrator (to version 24) should migrate: false - up
15:37:28.481 › Migrator ClearClipboardDelayMigrator (to version 25) should migrate: false - up
15:37:28.481 › Migrator RevertLastSyncMigrator (to version 26) should migrate: false - up
15:37:28.482 › Migrator BadgeSettingsMigrator (to version 27) should migrate: false - up
15:37:28.482 › Migrator MoveBiometricUnlockToStateProviders (to version 28) should migrate: false - up
15:37:28.482 › Migrator UserNotificationSettingsKeyMigrator (to version 29) should migrate: false - up
15:37:28.482 › Migrator PolicyMigrator (to version 30) should migrate: false - up
15:37:28.482 › Migrator EnableContextMenuMigrator (to version 31) should migrate: false - up
15:37:28.483 › Migrator PreferredLanguageMigrator (to version 32) should migrate: false - up
15:37:28.483 › Migrator AppIdMigrator (to version 33) should migrate: false - up
15:37:28.483 › Migrator DomainSettingsMigrator (to version 34) should migrate: false - up
15:37:28.483 › Migrator MoveThemeToStateProviderMigrator (to version 35) should migrate: false - up
15:37:28.483 › Migrator VaultSettingsKeyMigrator (to version 36) should migrate: false - up
15:37:28.484 › Migrator AvatarColorMigrator (to version 37) should migrate: false - up
15:37:28.484 › Migrator TokenServiceStateProviderMigrator (to version 38) should migrate: false - up
15:37:28.484 › Migrator MoveBillingAccountProfileMigrator (to version 39) should migrate: false - up
15:37:28.484 › Migrator OrganizationMigrator (to version 40) should migrate: false - up
15:37:28.484 › Migrator EventCollectionMigrator (to version 41) should migrate: false - up
15:37:28.485 › Migrator EnableFaviconMigrator (to version 42) should migrate: false - up
15:37:28.485 › Migrator AutoConfirmFingerPrintsMigrator (to version 43) should migrate: false - up
15:37:28.485 › Migrator UserDecryptionOptionsMigrator (to version 44) should migrate: false - up
15:37:28.485 › Migrator MergeEnvironmentState (to version 45) should migrate: false - up
15:37:28.486 › Migrator DeleteBiometricPromptCancelledData (to version 46) should migrate: false - up
15:37:28.486 › Migrator MoveDesktopSettingsMigrator (to version 47) should migrate: false - up
15:37:28.486 › Migrator MoveDdgToStateProviderMigrator (to version 48) should migrate: false - up
[141405:0502/153728.562863:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[141405:0502/153728.562949:ERROR:select_file_dialog_linux_portal.cc(285)] Failed to read portal version property
15:37:30.098 › State version: 48
15:37:30.116 › Error: No password found
15:37:30.119 › Error: No password found
15:37:30.128 › Error: No password found
15:37:30.128 › Error: No password found
15:37:30.151 › Error: No password found
15:37:30.164 › Error: No password found
15:37:30.164 › Error: No password found
15:37:30.204 › Error: No password found
15:37:30.204 › Error: No password found
15:37:30.206 › Error: No password found
15:37:30.246 › Error: No password found
15:37:30.247 › Error: No password found
15:37:30.254 › Error: No password found
15:37:30.259 › Error: No password found
15:37:30.260 › Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts
15:37:30.269 › Error: No password found
15:37:30.271 › Error: No password found
15:37:30.287 › Error: No password found
15:37:30.366 › Error: No password found
15:37:31.191 › Error: No password found
15:37:31.193 › Error: No password found
15:37:31.194 › Error: No password found
(node:141405) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu')
    at TrayMain.updateContextMenu (/usr/lib/bitwarden/app.asar/main.js:88410:23)
    at MessagingMain.updateTrayMenu (/usr/lib/bitwarden/app.asar/main.js:87873:28)
    at MessagingMain.onMessage (/usr/lib/bitwarden/app.asar/main.js:87795:22)
    at MessagingMain.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:87783:155)
    at Generator.next (<anonymous>)
    at /usr/lib/bitwarden/app.asar/main.js:87760:71
    at new Promise (<anonymous>)
    at messaging_main_awaiter (/usr/lib/bitwarden/app.asar/main.js:87756:12)
    at IpcMainImpl.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:87783:83)
    at IpcMainImpl.emit (node:events:517:28)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:141405) 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: 1)
15:37:33.165 › Error: No password found
15:37:33.167 › Error: No password found
15:37:39.340 › Error: No password found
15:37:39.357 › Error: No password found
15:37:39.362 › Error: No password found
15:37:39.364 › Error: No password found
15:37:39.368 › Error: No password found
15:37:39.376 › Error: No password found
15:37:39.378 › Error: No password found
15:37:39.382 › Error: No password found
15:37:39.404 › Error: No password found
15:37:39.406 › Error: No password found
(node:141405) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu')
    at TrayMain.updateContextMenu (/usr/lib/bitwarden/app.asar/main.js:88410:23)
    at MessagingMain.updateTrayMenu (/usr/lib/bitwarden/app.asar/main.js:87873:28)
    at MessagingMain.onMessage (/usr/lib/bitwarden/app.asar/main.js:87795:22)
    at MessagingMain.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:87783:155)
    at Generator.next (<anonymous>)
    at /usr/lib/bitwarden/app.asar/main.js:87760:71
    at new Promise (<anonymous>)
    at messaging_main_awaiter (/usr/lib/bitwarden/app.asar/main.js:87756:12)
    at IpcMainImpl.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:87783:83)
    at IpcMainImpl.emit (node:events:517:28)
(node:141405) 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)
15:37:39.423 › Error: No password found
15:37:39.437 › Error: Failed to decode access token: JWT must have 3 parts
15:37:40.132 › Error: No password found
15:37:50.132 › Error: No password found
15:38:00.132 › Error: No password found
15:38:10.133 › Error: No password found

Hope that something can be done. Love the project!!!!

[trmartin4]

Hello!

We are actively working on a solution to this problem. The solution will be implemented with https://github.com/bitwarden/clients/pull/8913, which is currently in final development. We will need to through remaining development, QA and release, so I cannot commit to a particular date at this point.

We appreciate your patience as we work through a solution to this issue.

[sjuliancarrizo]

I had the same issue on Kubuntu 22.04.4 LTS (KDE). The fix mentioned above did not work for me until I installed gnome-keyring. It seems as if older versions of kwallet do not support the org.freedesktop.secrets DBus API, which seems to be necessary for Bitwarden to work properly.

I can confirm this in Kubuntu 22.04.4 LTS (KDE). Steps: 1_ sudo apt install gnome-keyring 2_ Download Appimage from Bitwarden website. 3_ At the first run, keyring asks to create a password. Just give one and then the app starts and works fine.

[trmartin4]

Hello,

For anyone experiencing this issue, we have a build available if you would like to download and verify that you are able to log in successfully without necessarily installing gnome-keyring or kwallet. This is a non-production build still in review, so we do advise that you back up your vault before using.

The change will detect whether there are issues with the OS credential store (Secrets Service in this case) and fall back to disk storage for the access token and refresh token if there are any problems storing it. Secure storage is the preference and the default, but we recognize that there may be circumstances in which that mechanism is not available and we need to support it without preventing the user from accessing their vault.

We are continuing to investigate the root cause of the reports of inconsistent behavior with Secrets Service implementations so that we can reduce the necessity to fall back to only the minimum possible number of users.

[ThomasBoom89]

Hello,

For anyone experiencing this issue, we have a build available if you would like to download and verify that you are able to log in successfully without necessarily installing gnome-keyring or kwallet. This is a non-production build still in review, so we do advise that you back up your vault before using.

The change will detect whether there are issues with the OS credential store (Secrets Service in this case) and fall back to disk storage for the access token and refresh token if there are any problems storing it. Secure storage is the preference and the default, but we recognize that there may be circumstances in which that mechanism is not available and we need to support it without preventing the user from accessing their vault.

We are continuing to investigate the root cause of the reports of inconsistent behavior with Secrets Service implementations so that we can reduce the necessity to fall back to only the minimum possible number of users.

Hello, i am running arch linux without gnome-keyring and without kwallet. Current bitwarden desktop version bitwarden 2024.4.3-1 doesn't work and shows the same error:

1. Error: Failed to decode access token: JWT must have 3 parts
2. Error: The name is not activatable

I tested the build you mentioned and was able to log in and also synchronize my vault, so this build seems to fix the problem, at least for me. Thank you!

[tabascosw]

The mentioned build works for me as well.