Add --no-sandbox option to desktop files #1707
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Did you confirm that it didn't work before this change and then it worked with the change? |
feross
reviewed
Sep 19, 2019
Yes, I've been able to reproduce the whole issue and the fix following the steps described here. |
hicom150
force-pushed
the
no_sandbox
branch
from
1043dc8 to
f65fc68
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[x] Bug fix
[ ] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
Add
--no-sandboxoption to launch scripts (Desktop files) to temporary fix #1703 issue.Is there anything you'd like reviewers to focus on?
Check on different platforms. I've checked successfully in Ubuntu 18.04.3 LTS and Debian 8 Jessie