Session keys missing - I am told to log out and log in again.

[Biep]

Steps to reproduce

I click the Element Desktop icon in the start bar, and am told that there are no session keys. I should log out and in again - and can report this if I first create an issue here. (This is from memory, as a modal window "Send logs" prevents me from checking the details.) I expect the logs will contain the data needed.

Outcome

What did you expect?

To see my rooms

What happened instead?

See above.

Operating system

Linux 22.04

Application version

Cannot check right now, but should be the latest.

How did you install the app?

From the repo.

Homeserver

synod.im

Will you send logs?

Yes

[Biep]

Element-versie: 1.11.36
Olm-versie: 3.2.14

After logging out and in again - and verifying for the sake of my server backup - some settings were lost (e.g. showing the first line of the last message in the room bar to the left, and showing rooms with unread messages first).
And past messages in encrypted rooms show as "Unable to decrypt message" - without a button to ask other sessions for the keys.

[Biep]

I opened a dormant web session, and there the messages are lisible.
Reloading the cache repaired the Desktop session - but reloading is not smooth, as during the reload error messages are created, which resolve themselves once the cache is loaded again.

[t3chguy]

From the repo.

What repo? There are many.

[Biep]

Does this help? I couldn't copy text - sorry.

[t3chguy]

Duplicate of #692

[Biep]

I was very definitely not low on disk space - over 50 GB free.

[t3chguy]

@Biep Chrome's quota is based on a percentage, not an absolute amount. 50GB can be low enough to trigger chrome (electron) quota.

[Biep]

So if my disk is large enough, any amount of free space can trigger this? That sounds like a serious bug..

[t3chguy]

@Biep you'd need to ask Chrome/ium on what heuristics they use, I don't think they're published anywhere