-
Notifications
You must be signed in to change notification settings - Fork 130
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
Start AppImage with --no-sandbox option #414
base: master
Are you sure you want to change the base?
Conversation
I don’t have a reproducer system for the issue. I started the current AppImage with
When I start the adjusted AppImage, it looks like this:
It looks like we have fewer processes with the So, I’m not certain this completely resolves the issue, but as mentioned I wasn’t able to properly test it. |
OK, I downloaded your branch from:
|
Without this the AppImage is not running properly on newer Ubuntu versions. For more information see #363.
I downloaded and extracted this file:
I put it in a location explicitly not covered by my custom profile in /etc/apparmor.d/theia. Running it in a console prints:
So I fear, this is a bummer ... BTW: Moving it to the location covered by my apparmor-profile, it starts up normally and reports as: But this is not what you were hoping for ... And I can also run with explicit "--no-sandbox" parameter - but if I understood your intention correctly, the parameter shall explicitly not be necessary, right? More versions:
|
Thank you for trying it out. That probably means, that we set the --no-sandbox flag to late. I am actually not sure if we then can still ship a AppImage and solve this issue. We will need to investigate that. |
What it does
Without this the AppImage is not running properly on newer Ubuntu versions. For more information see #363.
How to test
yarn && yarn build && yarn download:plugins && yarn electron package
)--no-sandbox
option--no-sandbox
option is not presentReview checklist
Reminder for reviewers