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

Linux desktop version will not start or send logs after latest update. #6935

Closed
ianp5uk opened this issue May 14, 2024 · 5 comments
Closed
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues ios issues that concern the ios client but not all clients state:tested We tested it and are about to release it
Milestone

Comments

@ianp5uk
Copy link

ianp5uk commented May 14, 2024

Linux desktop version will not start or send logs after latest update. App launches to error, blank screen just inviting error report which it can't send. Today is Tuesday, 14th May.
Ubuntu 22.04.4

@ianp5uk ianp5uk added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels May 14, 2024
@charlag
Copy link
Contributor

charlag commented May 14, 2024

Hi, thank you for the report. Do you see any output in the terminal?

@bedhub
Copy link
Contributor

bedhub commented May 14, 2024

Stack trace of the initial error

Feedback v229.240513.0 - CryptoError - PAID - linux
Client: linux
Type: PAID
Tutanota version: 229.240513.0
Timestamp (UTC): Tue, 14 May 2024 08:51:16 GMT
User agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) tutanota-desktop/229.240513.0 Chrome/122.0.6261.156 Electron/29.3.2 Safari/537.36
CryptoError
Error message: mac expected but not present
Stacktrace:
CryptoError: mac expected but not present
at Gs (asset://app/worker.js:1:55216)
at Us (asset://app/worker.js:1:55039)
at Ba (asset://app/worker.js:7:46224)
at Lo.unlockUserGroupKey (asset://app/worker.js:18:51556)
at Ya.initSession (asset://app/worker.js:18:23348)
at async Ya.finishResumeSession (asset://app/worker.js:18:22625)
at async Ya.asyncResumeSession (asset://app/worker.js:18:21818)

@bedhub
Copy link
Contributor

bedhub commented May 14, 2024

Stack trace when trying to send the error

Feedback v229.240513.0 - Error - PAID - linux
Client: linux
Type: PAID
Tutanota version: 229.240513.0
Timestamp (UTC): Tue, 14 May 2024 08:52:26 GMT
User agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) tutanota-desktop/229.240513.0 Chrome/122.0.6261.156 Electron/29.3.2 Safari/537.36
Error
Error message: AssertNotNull failed : null
Stacktrace:
Error: AssertNotNull failed : null
at q (asset://app/common-min--qHbzLJQ.js:1:13440)
at Lo.getLoggedInUser (asset://app/worker.js:18:52947)
at MailFacade.createDraft (asset://app/worker-lazy-oMVeY3qv.js:1:31714)
at asset://app/common-zoyYDbsu.js:1:4441

@synthgab
Copy link

Hi, it's the exact same behavior and error stack trace on Android. Maybe worth also labeling this issue 'android' ?
Thank you !

bedhub added a commit that referenced this issue May 14, 2024
…ent. #6935

When doing a login with offline data we initialize the user facade from offline cache.
In case another client changed the kdf type (argon2 migration) we need to update the user
facade as soon as we go online to unlock the user group key correctly.
github-merge-queue bot pushed a commit that referenced this issue May 14, 2024
…ent. #6935 (#6936)

When doing a login with offline data we initialize the user facade from offline cache.
In case another client changed the kdf type (argon2 migration) we need to update the user
facade as soon as we go online to unlock the user group key correctly.

Co-authored-by: bedhub <bedhub@users.noreply.github.com>
@bedhub
Copy link
Contributor

bedhub commented May 14, 2024

Ah, all clients with offline support are affected Android, iOS and Desktop client.

To reproduce.

  1. Precondition: Have a paid account with KDF type Bcrypt and and offline database with client version 227.x
  2. Login in with other client version 229.x to do the argon2 migration (while the offline database client is closed).
  3. Login with offline client and see that he error appears.

Affected versions

229.240513.0 and below

Fixed in

229.240514.1

Test notes

  • Create offline database with desktop client version 227.x using a paid account.
  • Shut down off desktop client and migrate kdf using web client
  • Start desktop client and upgrade to version 229.240514.1. Verify that there are no log in errors.

@bedhub bedhub added android issues that concern the android client but not all clients ios issues that concern the ios client but not all clients labels May 14, 2024
@bedhub bedhub added this to the 229.240514.0 milestone May 14, 2024
@bedhub bedhub added the state:tested We tested it and are about to release it label May 14, 2024
@bedhub bedhub closed this as completed May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues ios issues that concern the ios client but not all clients state:tested We tested it and are about to release it
Projects
None yet
Development

No branches or pull requests

4 participants