Open konomikitten opened 1 month ago
Not just GNOME, seeing this on latest KDE as well. Completely nuking ~/.var/app/im.riot.Riot temporarily fixes it, but it's a pain because you lose settings, have to verify session again etc, then it just breaks again after a couple of runs.
Same experience. I could successfully log in, quit the app and then I'm greeted with log in screen again :upside_down_face:
As pointed out here, have you checked that it's not running in background? https://github.com/element-hq/element-web/issues/18625#issuecomment-961994459
You can also check with:
flatpak ps
After closing Element if an instance of the flatpak remains.
As pointed out here, have you checked that it's not running in background? element-hq/element-web#18625 (comment)
Unfortunately for me Element was corrupting the session data as well, I did check multiple processes weren't running but I should've checked the logs. I haven't had the issue pop up while on Element 1.11.81
.
Is anyone else still having this problem?
Yes. It feels a bit hopeless.
If you press Send logs
and then Download logs
the error Element is encountering should be listed.
When I use Element on GNOME it breaks showing the endless spinner. This happens about 50% of the time when I start it and only started happening recently. This ends up with the session data breaking and needing to log back into the client. It doesn't seem to happen on my desktop that runs XFCE. Normally I'd report this to Element itself but because I already found an issue there telling me to report it against the Flatpak instead I'm reporting it here. The following issues seem related.