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

Desktop Startup "Unable to restore session" #17210

Closed
mirdaki opened this issue May 9, 2021 · 5 comments
Closed

Desktop Startup "Unable to restore session" #17210

mirdaki opened this issue May 9, 2021 · 5 comments
Labels

Comments

@mirdaki
Copy link

mirdaki commented May 9, 2021

Description

The last several times I've logged in to my Fedora desktop, Element has failed to restore it's session, and I need to fully re-login. In each case, Element was closed by me restarting the machine before me starting it again and seeing the message.

Steps to reproduce

  • Start Element

It should load up and restore my previous session.

Logs being sent: yes

image

Version information

  • Platform: Desktop

For the desktop app:

  • OS: Fedora 34
  • Version: 1.7.25

Thank you for developing Element!

@mirdaki
Copy link
Author

mirdaki commented May 9, 2021

It may not be related, but each time I've tried to do encryption verification from my phone via scanning the QR code, it fails and I have to do it again or it just takes several minutes to propagate.

@aaronraimist
Copy link
Collaborator

It is quite likely this is an issue with the community maintained Fedora package. The only Linux package that Element maintains is for Debian/Ubuntu. You should probably open an issue with the Fedora package that you are using.

@mirdaki
Copy link
Author

mirdaki commented May 10, 2021

Sure thing!

@omalaspinas
Copy link

omalaspinas commented Mar 24, 2022

I have the same problem on manjaro linux on one of my computers that appeared last week (just sent the logs). I'm running:

Element version: 1.10.6
Olm version: 3.2.8

@richvdh
Copy link
Member

richvdh commented Feb 16, 2024

Unsurprisingly, after 3 years, we no longer have the logs for this, so can't really tell what happened.

@richvdh richvdh closed this as completed Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants