Desktop/linux/kwallet6 - Master password unlock data was not found for the user

Tiban · February 8, 2026, 12:10pm

First of all, this is not one of the my master password suddenly does not work anymore posts. It works perfectly fine in browser or other devices.
The issue is that the desktop app on linux/aurora does not unlock properly. My guess is that it does not manage to save some information to the keyring.

Expected behavior:

login with email and password
lock the vault
login with password only (this fails)

What I have to do now is logout completely and log back in with email and password again.
I copied the password from step 3 to log back in and doublechecked it in cleartext so it should definitely be the same

–

Operating System: Aurora 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.17.12-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics

Bitwarden Version 2026.1.0
I tried Flatpak, AppImage and rpm via rpm-ostree, all had the same behavior

I use kwallet6 with default setting

–

This is the log from rpm:

➜ bitwarden
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: rpm
12:28:00.522 › State version: 74
12:28:00.524 › Migrator MinVersionMigrator (to version 3) should migrate: false - up
12:28:00.524 › Migrator RemoveEverBeenUnlockedMigrator (to version 4) should migrate: false - up
12:28:00.525 › Migrator AddKeyTypeToOrgKeysMigrator (to version 5) should migrate: false - up
12:28:00.525 › Migrator RemoveLegacyEtmKeyMigrator (to version 6) should migrate: false - up
12:28:00.525 › Migrator MoveBiometricAutoPromptToAccount (to version 7) should migrate: false - up
12:28:00.525 › Migrator MoveStateVersionMigrator (to version 8) should migrate: false - up
12:28:00.525 › Migrator MoveBrowserSettingsToGlobal (to version 9) should migrate: false - up
12:28:00.525 › Migrator EverHadUserKeyMigrator (to version 10) should migrate: false - up
12:28:00.526 › Migrator OrganizationKeyMigrator (to version 11) should migrate: false - up
12:28:00.526 › Migrator MoveEnvironmentStateToProviders (to version 12) should migrate: false - up
12:28:00.526 › Migrator ProviderKeyMigrator (to version 13) should migrate: false - up
12:28:00.526 › Migrator MoveBiometricClientKeyHalfToStateProviders (to version 14) should migrate: false - up
12:28:00.526 › Migrator FolderMigrator (to version 15) should migrate: false - up
12:28:00.526 › Migrator LastSyncMigrator (to version 16) should migrate: false - up
12:28:00.526 › Migrator EnablePasskeysMigrator (to version 17) should migrate: false - up
12:28:00.526 › Migrator AutofillSettingsKeyMigrator (to version 18) should migrate: false - up
12:28:00.526 › Migrator RequirePasswordOnStartMigrator (to version 19) should migrate: false - up
12:28:00.526 › Migrator PrivateKeyMigrator (to version 20) should migrate: false - up
12:28:00.526 › Migrator CollectionMigrator (to version 21) should migrate: false - up
12:28:00.527 › Migrator CollapsedGroupingsMigrator (to version 22) should migrate: false - up
12:28:00.527 › Migrator MoveBiometricPromptsToStateProviders (to version 23) should migrate: false - up
12:28:00.527 › Migrator SmOnboardingTasksMigrator (to version 24) should migrate: false - up
12:28:00.527 › Migrator ClearClipboardDelayMigrator (to version 25) should migrate: false - up
12:28:00.527 › Migrator RevertLastSyncMigrator (to version 26) should migrate: false - up
12:28:00.527 › Migrator BadgeSettingsMigrator (to version 27) should migrate: false - up
12:28:00.527 › Migrator MoveBiometricUnlockToStateProviders (to version 28) should migrate: false - up
12:28:00.527 › Migrator UserNotificationSettingsKeyMigrator (to version 29) should migrate: false - up
12:28:00.527 › Migrator PolicyMigrator (to version 30) should migrate: false - up
12:28:00.527 › Migrator EnableContextMenuMigrator (to version 31) should migrate: false - up
12:28:00.527 › Migrator PreferredLanguageMigrator (to version 32) should migrate: false - up
12:28:00.527 › Migrator AppIdMigrator (to version 33) should migrate: false - up
12:28:00.527 › Migrator DomainSettingsMigrator (to version 34) should migrate: false - up
12:28:00.528 › Migrator MoveThemeToStateProviderMigrator (to version 35) should migrate: false - up
12:28:00.528 › Migrator VaultSettingsKeyMigrator (to version 36) should migrate: false - up
12:28:00.528 › Migrator AvatarColorMigrator (to version 37) should migrate: false - up
12:28:00.528 › Migrator TokenServiceStateProviderMigrator (to version 38) should migrate: false - up
12:28:00.528 › Migrator MoveBillingAccountProfileMigrator (to version 39) should migrate: false - up
12:28:00.528 › Migrator OrganizationMigrator (to version 40) should migrate: false - up
12:28:00.528 › Migrator EventCollectionMigrator (to version 41) should migrate: false - up
12:28:00.528 › Migrator EnableFaviconMigrator (to version 42) should migrate: false - up
12:28:00.528 › Migrator AutoConfirmFingerPrintsMigrator (to version 43) should migrate: false - up
12:28:00.528 › Migrator UserDecryptionOptionsMigrator (to version 44) should migrate: false - up
12:28:00.528 › Migrator MergeEnvironmentState (to version 45) should migrate: false - up
12:28:00.528 › Migrator DeleteBiometricPromptCancelledData (to version 46) should migrate: false - up
12:28:00.528 › Migrator MoveDesktopSettingsMigrator (to version 47) should migrate: false - up
12:28:00.529 › Migrator MoveDdgToStateProviderMigrator (to version 48) should migrate: false - up
12:28:00.529 › Migrator AccountServerConfigMigrator (to version 49) should migrate: false - up
12:28:00.529 › Migrator KeyConnectorMigrator (to version 50) should migrate: false - up
12:28:00.529 › Migrator RememberedEmailMigrator (to version 51) should migrate: false - up
12:28:00.529 › Migrator DeleteInstalledVersion (to version 52) should migrate: false - up
12:28:00.529 › Migrator DeviceTrustServiceStateProviderMigrator (to version 53) should migrate: false - up
12:28:00.529 › Migrator SendMigrator (to version 54) should migrate: false - up
12:28:00.529 › Migrator MoveMasterKeyStateToProviderMigrator (to version 55) should migrate: false - up
12:28:00.529 › Migrator AuthRequestMigrator (to version 56) should migrate: false - up
12:28:00.529 › Migrator CipherServiceMigrator (to version 57) should migrate: false - up
12:28:00.529 › Migrator RemoveRefreshTokenMigratedFlagMigrator (to version 58) should migrate: false - up
12:28:00.529 › Migrator KdfConfigMigrator (to version 59) should migrate: false - up
12:28:00.530 › Migrator KnownAccountsMigrator (to version 60) should migrate: false - up
12:28:00.530 › Migrator PinStateMigrator (to version 61) should migrate: false - up
12:28:00.530 › Migrator VaultTimeoutSettingsServiceStateProviderMigrator (to version 62) should migrate: false - up
12:28:00.530 › Migrator PasswordOptionsMigrator (to version 63) should migrate: false - up
12:28:00.530 › Migrator GeneratorHistoryMigrator (to version 64) should migrate: false - up
12:28:00.530 › Migrator ForwarderOptionsMigrator (to version 65) should migrate: false - up
12:28:00.530 › Migrator MoveFinalDesktopSettingsMigrator (to version 66) should migrate: false - up
12:28:00.530 › Migrator RemoveUnassignedItemsBannerDismissed (to version 67) should migrate: false - up
12:28:00.530 › Migrator MoveLastSyncDate (to version 68) should migrate: false - up
12:28:00.530 › Migrator MigrateIncorrectFolderKey (to version 69) should migrate: false - up
12:28:00.530 › Migrator RemoveAcBannersDismissed (to version 70) should migrate: false - up
12:28:00.530 › Migrator RemoveNewCustomizationOptionsCalloutDismissed (to version 71) should migrate: false - up
12:28:00.530 › Migrator RemoveAccountDeprovisioningBannerDismissed (to version 72) should migrate: false - up
12:28:00.530 › Migrator AddMasterPasswordUnlockData (to version 73) should migrate: false - up
12:28:00.530 › Migrator RemoveLegacyPin (to version 74) should migrate: false - up
(bitwarden-app:12042): Gtk-WARNING **: 12:28:00.573: Theme parsing error: gtk.css:2:33: Failed to import: Fehler beim Öffnen der Datei »/home/user/.config/gtk-3.0/window_decorations.css«: Datei oder Verzeichnis nicht gefunden
12:28:00.616 › [Process Isolation] Isolating process from debuggers and memory dumps
12:28:00.621 › [NAPI] [INFO] desktop_core::process_isolation::process_isolation: Disabling ptrace and memory access for main via PR_SET_DUMPABLE. pid=12042
12:28:00.624 › Coredumps are disabled in renderer process
12:28:01.502 › [Native Messaging IPC] Clearing connected apps
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:01.504 › State version: 74
12:28:01.508 › Unhandled error in angular Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:01.508 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden_auto [some-string]_user_auto
12:28:01.560 › Using SignalR for server notifications
12:28:01.587 › [TokenService] Error decrypting access token Error: The cipher’s MAC doesn’t match the expected value
12:28:01.588 › Failed to decrypt access token Error: The cipher’s MAC doesn’t match the expected value
(bitwarden-app:12042): IBUS-WARNING **: 12:28:01.622: Unable to connect to ibus: Die angegebene Adresse ist leer
12:28:01.659 › [TokenService] Error decrypting access token Error: The cipher’s MAC doesn’t match the expected value
12:28:01.660 › Failed to decrypt access token Error: The cipher’s MAC doesn’t match the expected value
12:28:01.660 › Error refreshing access token: Error: Access token not found.
12:28:01.661 › [TokenService] Error decrypting access token Error: The cipher’s MAC doesn’t match the expected value
12:28:01.661 › Failed to decrypt access token Error: The cipher’s MAC doesn’t match the expected value
12:28:01.662 › [SignalR] Failed to start the connection: Error: Failed to decode access token: Access token not found.
12:28:01.727 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:01.736 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:01.736 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:01.737 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:01.755 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:01.759 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.033 › Using SignalR for server notifications
12:28:02.042 › [TokenService] Error decrypting access token Error: The cipher’s MAC doesn’t match the expected value
12:28:02.043 › Failed to decrypt access token Error: The cipher’s MAC doesn’t match the expected value
12:28:02.049 › [TokenService] Error decrypting access token Error: The cipher’s MAC doesn’t match the expected value
12:28:02.049 › Failed to decrypt access token Error: The cipher’s MAC doesn’t match the expected value
12:28:02.049 › [SignalR] Failed to start the connection: Error: Failed to decode access token: Access token not found.
12:28:02.131 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.131 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.131 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.142 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.142 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.143 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:02.155 › Active account changed, clearing SSH keys
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:02.159 › Failed to clear SSH keys Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:02.201 › Active account changed, clearing SSH keys
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:02.216 › Retrieving application id
12:28:02.217 › Failed to clear SSH keys Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:02.218 › Reloading render process
[12102:0208/122802.218996:FATAL:content/child/child_thread_impl.cc:377] Crashing because hung
12:28:02.219 › Reloading render process
12:28:02.287 › Render process reloaded
12:28:02.288 › Render process reloaded
12:28:02.727 › [Native Messaging IPC] Clearing connected apps
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:02.728 › State version: 74
12:28:02.729 › Unhandled error in angular Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:02.732 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden_auto [some-string]_user_auto
12:28:02.847 › Retrieving application id
12:28:02.850 › Retrieving application id
12:28:05.680 › Retrieving application id
12:28:05.688 › Retrieving application id
12:28:12.460 › Retrieving application id
12:28:13.319 › [KeyService] Deriving master key took 550ms
12:28:13.324 › Retrieving application id
12:28:13.616 › Active account changed, clearing SSH keys
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:13.619 › Failed to clear SSH keys Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:13.639 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden [some-string]_accessTokenKey
12:28:13.662 › Using SignalR for server notifications
12:28:13.714 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:13.904 › [SignalR] WebSocket connected to wss://example.com/notifications/hub?access_token=[REDACTED]
12:28:13.904 › [SignalR] Using HubProtocol ‘messagepack’.
12:28:16.025 › Active account changed, clearing SSH keys
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:16.027 › Failed to clear SSH keys Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:16.254 › [EncryptedMigrationsScheduler] No migrations needed for user [some-string]
12:28:16.504 › [CipherService]: decrypt complete took 195.59999999962747 [ [ ‘Items’, 705 ] ]
12:28:16.703 › [SearchService]: index complete took 153.39999999990687 [ [ ‘Items’, 705 ] ]
12:28:16.798 › Error processing pending auth requests: [object Object]
12:28:19.174 › [LockService] Locking user [some-string]
12:28:19.240 › [NAPI] [INFO] desktop_core::password::password: OS keyring is_locked=false
12:28:19.253 › [LockService] Locked user [some-string]
12:28:19.319 › Reloading render process
[12277:0208/122819.323066:FATAL:content/child/child_thread_impl.cc:377] Crashing because hung
12:28:19.323 › Reloading render process
12:28:19.391 › Render process reloaded
12:28:19.391 › Render process reloaded
12:28:19.867 › [Native Messaging IPC] Clearing connected apps
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:107393)
at Session.emit (node:events:519:28)
12:28:19.868 › State version: 74
12:28:19.869 › Unhandled error in angular Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
12:28:19.873 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden_auto [some-string]_user_auto
12:28:19.907 › Using SignalR for server notifications
12:28:19.911 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden [some-string]_refreshToken
12:28:19.914 › [NAPI] [INFO] desktop_core::password::password: deleting legacy secret service entry service=“Bitwarden” account=“[some-string]_refreshToken”
12:28:20.124 › [SignalR] WebSocket connected to wss://example.com/notifications/hub?access_token=[REDACTED]
12:28:20.124 › [SignalR] Using HubProtocol ‘messagepack’.
12:28:26.264 › [MasterPasswordLockComponent] Failed to unlock via master password Error: Master password unlock data was not found for the user [some-string]

I believe the critical part is this one in line 130 and 171

12:28:02.218 › Reloading render process
[12102:0208/122802.218996:FATAL:content/child/child_thread_impl.cc:377] Crashing because hung
12:28:02.219 › Reloading render process

–

Thank you for any help

Nail1684 · February 8, 2026, 12:14pm

@Tiban Welcome to the forum!

Please post a screenshot of your Admin Dashboard.

Tiban · February 8, 2026, 12:19pm

This is for the client. If you need the server version too, I could probably get it but I am not hosting it myself

Nail1684 · February 8, 2026, 12:53pm

Yeah, the server version would be the necessary information.

When you don’t host it yourself, then I would also advise to contact the “Admin” of that server regarding this issue.

Tiban · February 8, 2026, 1:12pm

I think you already helped me a lot. I didn’t even consider that it could be a server problem because on other devices it worked fine.
I just tried the same with my bitwarden.eu account and it worked without problems.
I will contact my admin.
Thank you

Tiban · February 14, 2026, 11:25pm

Totally forgot to answer.
Long story short. He is running Vaultwarden and updated to the newest version and the problem is gone now. So no error with Bitwarden at all.
Thanks for the help

Nail1684 · February 15, 2026, 12:10am

It seems, you are using an unofficial server software, which is not supported by Bitwarden, as it is an independent product. From time to time, there will be compatibility issues between the official Bitwarden client apps (browser extension, mobile app, desktop app…) and an unofficial server product, when Bitwarden implements changes to its own server software and/or client apps. “…Bitwarden cannot guarantee that official clients will work perfectly with non-official servers.”

(Also due to this - and for other reasons - we recommend using the official Bitwarden server software.)

It is generally not possible for members of the Bitwarden community (users or developers) to help with such issues - and with issues of the unofficial server itself. Please seek support in their community spaces.

If you can replicate your issue on an official Bitwarden server, feel free to open a new thread here.