Login is not persistent

[RedXXIII]

Hello =) When first logging, I can tick a box to stay logged. However, and even if I do so, if I quit Zoom, I will have to log again. That bug is not happening with the deb or snap versions: I can close the app or even reboot the computer, my account stays logged in Zoom. I use Ubuntu 23.10 with the flatpak version of Zoom(5.17.5.2543).

[sudo-franko]

The problem was solved by removing the /.zoom directory from the deb or Snap version and restarting the program.

[choffee]

It seems to be a corruption of the database that zoom uses. You can remove ~/.zoom/data/zoomus.enc.v2.db when zoom is not running and it should start up okay. For the flatpak this translates to ~/.var/app/us.zoom.Zoom/data/zoomus.enc.v2.db similart to #446

This feels like an upstream bug as it happens with the deb package as well but with newer versions than 5.17.10 it seems like removing that DB might be a permanent fix. Might be something wrong with the 5.17.5 version?

[RedXXIII]

Bug is fixed with Ubuntu 22.04 (Flatpak 5.17.5.2543), thanks. I'll do the same with 23.10 and let you know.

[vwbusguy]

with newer versions than 5.17.10 it seems like removing that DB might be a permanent fix.

Unfortunately, I'm seeing this with 5.17.11.3835 on Fedora 39. If I delete the ~/.var/app/us.zoom.Zoom directory, I can then log in, but closing zoom and restarting it leads to being logged out and not being able to log back in until it's deleted again. Also, ~/.var/app/us.zoom.Zoom/data is then empty at this point.

[vwbusguy]

I just realized something! The flatpak is writing the database to ~/.zoom/data instead of to ~/.var/app/us.zoom.Zoom/data . So when you login the first time, the database is written to the wrong location for the flatpak and leads to a corrupt zoom, so when you restart zoom you lose the login and can't log in again because the database doesn't exist where zoom expects it to be.

This is unfortunately not the whole story, though. I tried rm -rf ~/.var/app/us.zoom.Zoom/ && ln -s ~/.zoom/ ~/.var/app/us.zoom.Zoom to sync ~/.zoom with the flatpak zoom home and still get this behavior.

It looks like on restart of zoom, zoom believes the original database it just created to be corrupt and then tries to fix it, but doesn't actually fix it:

-rw-------. 1 scott scott    75776 Mar 28 11:21 zoomus.enc.v2.db
-rw-------. 1 scott scott   102400 Mar 28 11:20 zoomus.enc.v2.db.malformed

Sometimes I've even been able to trigger this message right after the login:

Looking at the logs when zoom starts, it looks like there could be something going on with the secret storage in Gnome with seahorse as this warning hits journald on every subsequent zoom startup:
Mar 28 11:30:12 samus seahorse[690193]: key.vala:267: Key doesn't have a valid type

[RedXXIII]

Bug is fixed with Ubuntu 22.04 (Flatpak 5.17.5.2543), thanks. I'll do the same with 23.10 and let you know.

OK for me with with 23.10

[czhang03]

Can confirm, this works after I removed ~/.zoom (which zoom should no longer use or have access to, as of the latest version) and ~/.var/app/us.zoom.Zoom/.zoom/data/.

[majneb]

For me version flatpak 6.2.3 on Fedroa KDE is completely broken :

• SSO login is not remembered, even after removing ~/.zoom and ~/.var/app/us.zoom.Zoom,
• Once connected, clicking on New meeting does nothing.
  The native rpm works, but does not allow to to share individual screen or app (so not usable in a multi screen environment).
  So the only remaining working solution is zoom web interface (No problem with Firefox)

[vwbusguy]

6.2.3 just straight up crashes for me on KDE (Fedora 40 Kinoite) when I try to log in with SSO. Which I click SSO, it crashes when I type in the employer code before it even calls out to the browser.

[npt]

On 6.2.3.2056, this happened before I deleted ~/.var/app/us.zoom.Zoom/.zoom/data; it works after deleting that directory and logging in again.