search

flathub / im.riot.Riot

https://flathub.org/apps/details/im.riot.Riot
32 stars 43 forks source link

Logged out every time the application is fully closed #368

Open leafpool243 opened 1 year ago

leafpool243 commented 1 year ago

I’m getting logged out every single time I fully close the application which is quite annoying because I do often shut down my computer.

SISheogorath commented 1 year ago

This sounds like your access token isn't stored properly. Do you run a keyring service (e.g. gnome-keyring) on your desktop?

leafpool243 commented 1 year ago

@SISheogorath No, what’s that? (I’m using KDE Plasma by the way.)

ACiDGRiM commented 1 year ago

This sounds like your access token isn't stored properly. Do you run a keyring service (e.g. gnome-keyring) on your desktop?

I thought this might be the issue, so I reset the login keyring, logged out and back in. All of my apps such as brave, nextcloud, etc... were signed out (suggesting the keyring was working). But I can reproduce the issue, even after deleting the riot.im folder in .var

After I signin, verify and then quit Element, it opens back to the login page.

SISheogorath commented 1 year ago

When you exit, can you run flatpak ps and see if there is a lingering process remaining?

leafpool243 commented 1 year ago

I get this after I right-click the system tray and close it:

Instance   PID   Application             Runtime
3353440136 12141 im.riot.Riot            org.freedesktop.Platform
3376461948 12111 im.riot.Riot            org.freedesktop.Platform
1202893580 7785  org.keepassxc.KeePassXC org.kde.Platform
SISheogorath commented 1 year ago

Well, that sounds like the origin of the problem. There seems to be a lingering process which will corrupt the credentials cache. Can you try to use flatpak kill im.riot.Riot to close Element and see if the problem remains?

ACiDGRiM commented 1 year ago

Well, that sounds like the origin of the problem. There seems to be a lingering process which will corrupt the credentials cache. Can you try to use flatpak kill im.riot.Riot to close Element and see if the problem remains?

I can confirm that killing element with the flatpak kill command preserves the session across launches. Sometimes starting Element results in a window with the loading throbber and no logout link. But using flatpak kill and relaunching 2 or 3 times it will eventually load correctly

OS is Fedora 38 on gnome-shell

leafpool243 commented 1 year ago

I used flatpak kill im.riot.Riot and my session was preserved.

andreasdomanowski commented 11 months ago

I used flatpak kill im.riot.Riot and my session was preserved.

This unfortunately does not work with version 1.11.37.

kinghat commented 6 months ago

it wasnt that you were logged out, its that element wasnt really exited and starting it again tries using a new session vs the running one. i no longer have this issue on fedora 39 kde. it does show that element has crashed after i close it every time now though lol