SUID workaround #256
Closed
SUID workaround #256
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
Reduce errors produced in terminal from debian package installations by testing for existence of symlink prior to executing unlink
Add a workaround to allow the client to run without user intervention on Debian 10 and similar when failing due to the SUID chrome-sandbox error
|
@jfgordon2 this is an interesting approach, but sadly is only visible when you're developing in the repository - these scripts are not part of what we distribute to end users when they install the app. |
|
@shiftkey then back to the drawing board! |
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.
Workaround for #222
Description
If the client exits upon start, it will automatically attempt to re-launch with the
--no-sandboxtag as an attempt to address the SUID issue with Debian 10 and similar. This is a workaround to prefer automatically running the client instead of appearing to not work pending user intervention.Screenshots
Release notes
Notes: no-notes