Brave will not start on Arch Linux: No usable sandbox #9955
Comments
|
This bug also affects Debian (stretch). I cannot run the browser with sandboxing enabled (and I won't use it with sandboxing disabled). |
@aykevl did you try #6902 (comment) already? |
No, should test that. |
I'd agree. |
Same here on 4.12.6-1-ARCH. Chrome works, Brave not. |
same here on 4.12.8-2-ARCH |
I spoke to Sampson and we found a similar issue on Deepin Debian, getting a no usable sandbox error on version 0.18.23 |
@Lite5h4dow Thanks for tackling that issue with me. Just to add to your feedback, we were able to get Brave to run when we explicitly passed the |
yeah, thats what we ended up doing, im downloading the 19.3 beta to see if it has the same issue, ill update when i actually get it downloaded 👍 |
same issue 👎 no luck with 19.3 |
https://bugs.chromium.org/p/chromium/issues/detail?id=598454 https://bugs.chromium.org/p/chromium/issues/detail?id=312380 How to contact those guys assigned for the Chromium bug? I use Debian Stretch 9.1 |
@luixxiul Yes, I already did. Did not help at all... |
please paste the log of the error, thanks. |
@luixxiul Here you have it: |
Status please. |
For anyone that's struggling with this on Arch and doesn't want to do the insecure |
I'm seeing this problem in Debian testing/buster. I have a custom kernel (4.18.3) and the docs linked to in this error (https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md) don't clearly state what kernel config option needs to be enabled to get brave to work. Does someone here have this info? CONFIG_NAMESPACES is enabled. Then we can update the error message. Also, the document itself says that it's out of date. Brave should maintain their own copy of this if it's still relevant. Here's my error:
|
Nevermind, I found the kernel config option: |
With the new kernel, I also had a problem with running. Before updating the kernel, everything worked. [9829:9829:0827/152816.063604:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trap debugger/breakpoint (memory dump) |
@Redni that means that the |
I have in the kernel: |
For folks experiencing this, can you please try grabbing the new version of Brave? If you run still run into problems, let's create an issue in the new repository: |
I still experience the problem with version 0.56.12 OS is Debian 9.6 |
For Debian there is open issue at brave/brave-browser#1986 (comment) including a "workaround". |
Still happening on Manjaro with Linux 4.19.1
|
Just posted about this in various comments on this "issue"... In Artix OS, using "runit" / no systemd. Managed to get it installed using "yaourt", then got the namespace message about not being enabled. Then enabled it, then got "Trace/breakpoint trap" in terminal after trying to run "brave" in terminal. It appears in "Internet" menu and so forth, but just doesn't do anything. |
Leaving an update error log here, I know you're not supposed to do this but I did it anyway. I'm posting from Virtual Box with Artix Linux OS... I ran brave from terminal with sudo privs... then got these errors from terminal. Not sure if it answers any of the questions to above errors though..
|
Did you search for similar issues before submitting this one?
Yes. There are a number of bugs regarding this error message and extensive discussion at #6902. However, the only solution reported as successful involved enabling kernel user namespaces, which is awkward in Arch Linux so I'm hoping another chromium sandboxing method can be used.
The closest open bug is #7146 but this is specifically for Kali Linux.
Describe the issue you encountered:
After installing Brave from source, it won't run. See below for the error message, which says there is no usable chromium sandbox.
However, chromium is adequately sandboxed on my machine: opening chrome://sandbox shows:
The standard Arch Linux kernel does not have user namespaces enabled (a deliberate decision by maintainers). In order to enable this feature an Arch user must either recompile the kernel manually or install a custom kernel (though the corresponding AUR package linux-userns is out of date).
Is it possible for Brave to use SUID sandboxing instead? Or is it already trying to fall back to SUID sandboxing on my system (as chromium itself does) but failing for some reason?
Platform (Win7, 8, 10? macOS? Linux distro?):
Arch Linux 4.11.9 x86-64 (standard kernel)
Brave Version (revision SHA):
c8e92a1
Steps to reproduce:
yarn
)npm run watch
,npm start
)Actual result:
Expected result:
Brave browser starts normally.
Is this an issue in the currently released version?
yes
Can this issue be consistently reproduced?
yes
The text was updated successfully, but these errors were encountered: