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

Encryption Issue in Desktop App #16613

Closed
kattiara opened this issue Mar 5, 2021 · 5 comments
Closed

Encryption Issue in Desktop App #16613

kattiara opened this issue Mar 5, 2021 · 5 comments
Labels
A-E2EE A-Storage Storage layer of the app, including IndexedDB, local storage, etc. T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@kattiara
Copy link

kattiara commented Mar 5, 2021

Description

The desktop app of Element errors out for me after longish periods of inactivity. Something seems to be breaking the encryption, but not sure what. This happens every single night, overnight -- when I go to my computer in the morning, all previous messages show up like this:
element_error1_decryptfail

It happens every night, but I've also had it happen a couple times during the day when away from my computer for longish times (~5+ hours).

When this happens, it also seems to "break" the ability to log out from the desktop app -- clicking to try and sign out does nothing. The only fix I've found is to go into the mobile app, use that to terminate the desktop session, and then log back in to the desktop app. At that point everything looks normal again.

This is on a Windows 10 computer which is not set to sleep or hibernate.

These are my current security settings from the desktop app:
element_securitysettings1
element_securitysettings2

Steps to reproduce

  • Leave computer alone for 5+ hours, with Element desktop app running

Messages seem to "break" and don't display correctly until after force killing the desktop session (from mobile app) and relogging.

Logs being sent: yes

Version information

  • Platform:
    Desktop app - Windows 10, Element version: 1.7.22, olm version: 3.2.1
@kattiara
Copy link
Author

kattiara commented Mar 5, 2021

After creating the ticket, I tried to submit debug logs through the app, however, I now get another error message:

element_debuglogsendfail

@jryans
Copy link
Collaborator

jryans commented Mar 5, 2021

@kattiara Are you perhaps low on disk space? The transaction error suggests the app is having trouble writing to storage on disk.

@jryans jryans added A-Storage Storage layer of the app, including IndexedDB, local storage, etc. X-Needs-Info This issue is blocked awaiting information from the reporter labels Mar 5, 2021
@kattiara
Copy link
Author

kattiara commented Mar 5, 2021

@jryans Thanks for taking a look! I'm actually fine on disk space (~750+ GB free) atm, so don't think that's the issue.

@kattiara
Copy link
Author

kattiara commented Mar 5, 2021

I'm not sure if something else triggered it this time, but I actually just had it happen again without the longer period of inactivity:

element_shortfail

Note that at 5:40, I was able to send messages just fine. However, about half an hour later, the client had broken again, and responses to me were throwing the same error. Once again needed to forcekill the session and relog.

The user who was messaging me said that from their client, they were able to see the shield icon for me go red, indicating (I think) my encryption was broken.

@richvdh
Copy link
Member

richvdh commented Jan 12, 2023

duplicate of #14174 I think

@richvdh richvdh closed this as completed Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE A-Storage Storage layer of the app, including IndexedDB, local storage, etc. T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants