You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason for creating .zoom in home directory instead of sandboxing it? It seems to not contain any data that should be shared with other apps. Some flatpak'ed apps (like Firefox with .mozilla) have this kind of data persistently sandboxed (--persist=relative/path).
I moved .zoom to ~/.var/app/us.zoom.Zoom/ for my existing installation, then added the following overrides:
This issue is related to #18. Your suggested solution was introduced in #199 but later removed in f87bc46, which in turn comes from the beta branch's #217. I recall seeing a regression being discussed somewhere, but @TheEvilSkeleton did not reference any issue in the revert.
Is there any reason for creating
.zoom
in home directory instead of sandboxing it? It seems to not contain any data that should be shared with other apps. Some flatpak'ed apps (like Firefox with.mozilla
) have this kind of data persistently sandboxed (--persist=relative/path
).I moved
.zoom
to~/.var/app/us.zoom.Zoom/
for my existing installation, then added the following overrides:Don't see any difference in Zoom behavior, all the configuration is in place.
The text was updated successfully, but these errors were encountered: