Warning "--no-sandbox Stability and security will suffer" on first launch

[max-l]

I installed brave

Version 0.56.12 Chromium: 70.0.3538.77 (Official Build) unknown (64-bit)

as a ubuntu 18.04 snap: https://snapcraft.io/brave

When the browser launches there is the warning:

You are using an unsupported command-line flag --no-sandbox Stability and security will suffer

[rebron]

cc: @posix4e @diracdeltas @w0ts0n

[posix4e]

This is fixed in future snaps. The current snap needs an update.

[tomlowenthal]

How have you fixed it, @posix4e? Are you just not showing the warning any more?

[posix4e]

This is fixed in the current stable snap

[posix4e]

It was fixed here https://github.com/brave/unofficial-snap/commits/master for the last few commits.

• We upgraded to new brave
• We re-enabled the sandbox

[hubitor]

I have installed this version (dev version from AUR):
Version 0.61.17 Chromium: 72.0.3626.81 (Official Build) unknown (64-bit)
and I'm still seeing this message.
In which version will be the fix added?

[fmarier]

@hubitor That's because the package that's in Arch Linux explicitly disables the security sandbox when it detects that user namespaces are disabled.

To fix this, follow the instructions on the stable package page:

sudo sysctl kernel.unprivileged_userns_clone=1
echo kernel.unprivileged_userns_clone = 1 | sudo tee /etc/sysctl.d/00-local-userns.conf

[meliaas]

Hey, I followed @fmarier instructions but the error message persists on Manjaro Linux and Brave version 0.66.99-1

[fmarier]

@meliaas Could you please file a new issue for this and include:

• the version of Manjaro you are using
• the exact instructions you followed to install Brave
• the error message you are seeing when you run brave-browser from a terminal

I'd like to figure out what's not working for you since it appears to be different.

[fmarier]

I'm going to set this to P5 since the original reports were about unsupported third-party packages. The Manjaro issue is potentially different so we can track that separately.

[fmarier]

Closing since this was fixed a while back: #2979 (comment)