-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Element Web R stuck on syncing, on refresh rooms start appearing only when someone sense a message, after enabling Rust encryption #26604
Comments
Refresh shouldn't log you out. Something else happened. The slow initial sync and bad room state should be fixed by matrix-org/matrix-js-sdk#3830 that has landed in element-web 1.11.50 |
Looking at the rageshake logs:
... That matches exactly what I would expect to see if you had deliberately logged out from the client, and seems to have happened before you refreshed the application. |
Logging out must have happened because I had not opened Element Web on that browser for a while or something. I have now updated to .50. If I enable Rust encryption, I can log in, but previous encrypted messages show as undecryptable. Is this expected? |
that doesn't seem to be what the logs show...
It is expected that previous messages show as undecryptable on a new device, unless/until the keys can be downloaded from backup or retrieved from another device. We are continuing to work on the performance of Web R in this area. |
Actually I may have been looking at the wrong bit of the log, but I see something very similar happening earlier:
This looks to be the point that your client switched over to Rust crypto. You had been using that session for 15 seconds (with legacy crypto) up to that point. The next refresh happened at 17:12:01. I don't think we need to dig into exactly what happened, but the point is: I'm pretty sure the logout is not connected with enabling rust crypto in the config. |
Thank you so much for looking so deep into it! The experience was that I enabled Rust encryption, then opened my Element Web, it spent a second or two loading and then it showed me the login screen (even though last time I had used it, it was left logged in), so in my initial post I assumed being logged off was something that enabling Rust encryption did - however, that doesn't really matter; I read that the setting persists when you are logged in so I would have logged out anyway to get Rust encryption to switch on. The main problem was the infinite syncing and then rooms being gone, which .50 fixed.
|
Steps to reproduce
Enable rust encryption feature flag in config.json.
Refresh Element Web.
It logs me out, so I log back in.
It's stuck on syncing for a long time (longest I waited was 20 minutes).
Refresh, then it is logged in but it's empty. Rooms start showing only when someone else sends a message in the room.
Rooms are called " and 600 others" or similar, instead of their real names.
Then more rooms show (upon refreshing again), with the same name structure, under 'Historical', as if I have left them or not joined them.
Disabling the Rust encryption flag and logging in again makes everything appear normal.
Outcome
What did you expect?
I expected all my rooms and messages to show up as normal.
What happened instead?
Rooms only started appearing if someone else sent a message in that room. Room names were like " and 600 others" instead of the real name of the room.
Operating system
Debian server for hosting Element Web, Windows 10 for client browser
Browser information
Firefox 119.0.1
URL for webapp
1.11.49
Application version
1.11.49
Homeserver
Synapse 1.96.1
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: