Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitwarden AppImage crashes, cant get in to my vault #13019

Open
1 task
snowplow569 opened this issue Jan 22, 2025 · 2 comments
Open
1 task

Bitwarden AppImage crashes, cant get in to my vault #13019

snowplow569 opened this issue Jan 22, 2025 · 2 comments
Labels
bug desktop Desktop Application

Comments

@snowplow569
Copy link

Steps To Reproduce

Version 2025.1.1
SDK ‘main (28c7e29)’
Shell 33.2.1
Renderer 130.0.6723.137
Node 20.18.1
Architecture x64

I have been using bitwarden (bitwarden.com server) without an issue on fedora (40 Workstation, gnome 46 wayland Linux 6.12.9-100.fc40.x86_64) with AppImages for quite a while but since last update just after pressing enter after my password it crashes without any warning and closes. I did increased my encryption key settings but years ago I use: Argon2id, KDF iterations 6, KDF memory 1024, KDF parallelism 4. My guess is last update did something that limits maybe memory or something? As I could not find anything about this on the internet is not a common issue. I did erase the .config/Bitwarden folder to see if there was a corruption or something there but the crash persists.

To reproduce try to login with your data and it crashes after pressing enter after typing your password

last part of app.log (the last thing i did was try to log and it crashed so it should be here at the end)
[2025-01-22 16:34:34.896] [info] Migrator PasswordOptionsMigrator (to version 63) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator GeneratorHistoryMigrator (to version 64) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator ForwarderOptionsMigrator (to version 65) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator MoveFinalDesktopSettingsMigrator (to version 66) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator RemoveUnassignedItemsBannerDismissed (to version 67) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator MoveLastSyncDate (to version 68) should migrate: false - up
[2025-01-22 16:34:35.238] [info] Coredumps are disabled in renderer process
[2025-01-22 16:34:37.735] [info] State version: 68
[2025-01-22 16:34:37.829] [info] Retrieving application id
[2025-01-22 16:34:40.381] [info] Checking for update
[2025-01-22 16:34:41.615] [info] Update for version 2025.1.1 is not available (latest version: 2025.1.1, downgrade is disallowed).
[2025-01-22 16:34:46.130] [info] Retrieving application id

Expected Result

I should be asked for my 2fa and let me login afterwards.

Actual Result

the software crashes without a popup or warning it just disappears from screen.

bitwarden_error.mp4

Screenshots or Videos

No response

Additional Context

No response

Operating System

Linux

Operating System Version

Fedora 40 Workstation, gnome 46, wayland, Linux 6.12.9-100.fc40.x86_64

Installation method

Direct Download (from bitwarden.com)

Build Version

Version 2025.1.1 SDK 'main (28c7e29)' Shell 33.2.1 Renderer 130.0.6723.137 Node 20.18.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.
@snowplow569 snowplow569 added bug desktop Desktop Application labels Jan 22, 2025
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-17450

@snowplow569
Copy link
Author

snowplow569 commented Jan 22, 2025

I just tried with a new account without changing key settings and I was able to login so it has to do with something related to memory or something that is now limited.
then i tried changing to argon and this different options:

KDF iterations 6, KDF memory 64, KDF parallelism 4/
KDF iterations 6, KDF memory 512, KDF parallelism 4/
KDF iterations 6, KDF memory 768, KDF parallelism 4/
KDF iterations 6, KDF memory 896, KDF parallelism 4/
KDF iterations 6, KDF memory 999, KDF parallelism 4/
KDF iterations 6, KDF memory 1000, KDF parallelism 4/
KDF iterations 6, KDF memory 1012, KDF parallelism 4/
KDF iterations 6, KDF memory 1018, KDF parallelism 4/
KDF iterations 6, KDF memory 1021, KDF parallelism 4/
KDF iterations 6, KDF memory 1023, KDF parallelism 4/
KDF iterations 6, KDF memory 1024, KDF parallelism 4X

just the one with 1024 memory did not let me get in being 1024 the limit of KDF memory allowed to use but the AppImage does not allowed the 1024 but it does 1023 of memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug desktop Desktop Application
Projects
None yet
Development

No branches or pull requests

3 participants
@bitwarden-bot @snowplow569 and others