mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1896] zoom: attachments/calls/preferences #1274
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1274
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drzraf on GitHub (Apr 18, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1896
I found that the following isn't working in Zoom:
I tried to
noblacklist /tmp/qtsingleapp-zoom*since such (socket) files are used. No success.
Neither did
whitelist ${HOME}/Documents/Zoommade it work.Note: using firejail, attachment content is dumped raw inside terminal
Call. The "meet" button does not work.
Preferences: simply are not saved.
Groups: Can't create a chat group of several people
( @WeiGuoZoom / https://github.com/zoom ?)
@SkewedZeppelin commented on GitHub (Apr 22, 2018):
What version of Firejail are you using?
@drzraf commented on GitHub (Apr 22, 2018):
0.9.50 on Debian Stretch
zoom.profile:
@smitsohu commented on GitHub (May 5, 2018):
Can you try it again with
private-tmpcommented out?Failing that, does
firejail --ignore=whitelist zoomorfirejail --ignore=blacklist zoomrestore functionality?@chiraag-nataraj commented on GitHub (May 19, 2019):
Is this still an issue @drzraf?
@chiraag-nataraj commented on GitHub (May 21, 2019):
I'm going to go ahead and close for inactivity. @drzraf, please feel free to re-open if you still have this issue and can help us debug further.