-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Messages get completely stuck at "Encrypting your message" #24612
Comments
Looking at a recent rageshake which exhibits this (https://github.com/matrix-org/element-web-rageshakes/issues/19899), it seems like we've got stuck trying to make an Olm session for a particular device, and all attempts at encryption for this device are then blocking. Unfortunately the logs don't seem to go back far enough to show it getting stuck. The code which manages this is in Ideally, we would refactor it so that we can be more certain that it will catch all the error cases, but that's a non-trivial amount of work, and we're going to replace this bit of code for #21972. I'd still be interested in rageshakes from anyone seeing this behaviour, as they might point towards a quick fix. |
I restarted Element Desktop Nightly and the 2 stuck messages disappeared, while the UTDs are now decrypted with a grey shield. |
FWIW, the first time I encountered this issue in a rageshake was shortly after matrix-org/matrix-js-sdk#3035 landed, which looks like it might touch some relevant code, but I didn't see anything in that PR that looked like it could cause this breakage. I don't remember seeing any reports of this before that time, so it seems to be a recent issue. |
so as of now all of my messages stay on this state so far even after waiting a hour and re trying i am not been able to send a single message |
The rust cryptography stack will resolve this issue. |
(To use the rust cryptography stack, assuming you are on a recent version of Element, log out and in again.) |
Note: this is distinct from #15476, in which messages are slow to send but do get sent eventually.
There is a bug in which sometimes the encryption process gets completely stuck, with messages staying in the "encrypting" state for 15 minutes or more.
The text was updated successfully, but these errors were encountered: