-
Notifications
You must be signed in to change notification settings - Fork 50
Install zoomus.conf to app #143
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
Conversation
|
Started test build 17655 |
|
Build 17655 failed |
|
Started test build 17656 |
|
Build 17656 failed |
|
Started test build 17657 |
|
Build 17657 failed |
|
Started test build 17658 |
|
Build 17658 failed |
|
Started test build 17659 |
|
Build 17659 successful |
|
Started test build 17665 |
|
Build 17665 successful |
|
Started test build 17669 |
|
Build 17669 failed |
|
Started test build 17671 |
|
Build 17671 successful |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solved my issue 👍
Comment describing my successful test #22 (comment)
|
Started test build 17672 |
|
Build 17672 successful |
|
I tried the latest build and I can confirm that |
|
I think this would need |
|
Started test build 18703 |
|
Build 18703 successful |
|
Any update on this? I've MR'd to prevent rw access to $HOME and move I can't tell if this is MR is inactive or not, which is why I am asking. It would be cool if we could harden the sandbox first to prevent some security issues, and then fix this. EDIT: I am a GitLab user. I use MR instead of PR. Sorry for that |
|
This MR is pending review. |
|
Shall I close mine? |
|
I don't mind one way or another. |
|
Is this one working well or not? |
|
bot, build |
|
Queued test build for us.zoom.Zoom. |
|
Started test build 28474 |
|
Build 28474 successful |
|
Doesn't seem to work for me :( |
|
Closing in favor of #188 |
This changes sandbox enough that we can install app-vendored zoomus.conf that should workaround #22