Package Details: brave-bin 1:1.78.102-1

Git Clone URL: https://aur.archlinux.org/brave-bin.git (read-only, click to copy)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release)
Upstream URL: https://brave.com
Keywords: brave browser
Licenses: BSD, MPL2, custom:chromium
Conflicts: brave
Provides: brave, brave-browser
Submitter: toropisco
Maintainer: brave
Last Packager: brave
Votes: 875
Popularity: 17.39
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-05-15 16:26 (UTC)

Dependencies (8)

Required by (9)

Sources (4)

Pinned Comments

brave commented on 2025-04-25 13:00 (UTC)

Latest Comments

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 61 Next › Last »

whezzel commented on 2018-11-24 08:44 (UTC)

I use Cinnamon DE and had similar issues. I was able to fix it by editing ~/.config/mimeapps.list and changing all occurrences of chromium.desktop (my previous browser) to brave-bin.desktop, and deleting all the BraveBrowser data stored in ~/.cache and ~/.config.

I'm not sure why, but brave bugged me, for several days, about setting it to default, but a friend of mine said he only clicked 'Set as Default' once and it stopped asking him.

async commented on 2018-11-24 00:48 (UTC)

Any idea why this package always complains that it is not set to the default browser, even when it actually is? Using Gnome, fwiw.

whezzel commented on 2018-11-23 23:58 (UTC)

@simonorono Awesome. Thanks for such a quick fix

simonorono commented on 2018-11-23 16:57 (UTC)

I just solved that issue on version 0.56.15 @whezzel

whezzel commented on 2018-11-23 12:14 (UTC)

I understand the reason for the brave-bin.sh script, is to notify the user that the browser is not running in a sandbox which can be insecure. I have applied the fix listed in the 'pinned' comment so that my browser runs in a sandbox.

My question is, would it be possible to modify brave-bin.sh to pass additional flags to /usr/lib/brave-bin/brave?

For example:

brave --incognito     # opens a new brave window with a url of --incognito
/usr/lib/brave-bin/brave --incognito     # opens a new window in incognito mode.

Unfortunately, I'm not that great with scripting yet, otherwise I would try to make this modification on my own.

simonorono commented on 2018-11-17 19:41 (UTC) (edited on 2018-11-17 19:42 (UTC) by simonorono)

@Vrakfall the main Brave executable gets installed at /usr/lib/brave-bin/brave and will not run unless:

1) it finds a way of sandboxing the processes or 2) it's run with the --no-sandbox flag (very insecure)

The brave-bin.sh checks if you have user namespaces enabled; if not then it will run Brave with the --no-sandbox flag.

This is a known issue: https://github.com/brave/browser-laptop/issues/9955

If you try to run the main Brave executable with no flags you get this:

[23868:23868:1117/153840.810367:FATAL:zygote_host_impl_linux.cc(116)] 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.
Trace/breakpoint trap (core dumped)

Vrakfall commented on 2018-11-17 14:34 (UTC)

I can't find which command this flag is from. What is it linked to? I find it weird you advice using a kernel feature that weakens it.

async commented on 2018-11-16 05:56 (UTC)

Looks like there is an error in the desktop file... in Gnome, the desktop file opens a duplicate icon in the dock when added to favorites.

simonorono commented on 2018-11-15 03:35 (UTC) (edited on 2018-11-15 03:35 (UTC) by simonorono)

To disable the message telling "that you're using an unsupported command-line flag --no-sandbox" you must enable user namespaces with sysctl:

sudo sysctl kernel.unprivileged_userns_clone=1

To make it persist after reboot:

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

alerque commented on 2018-11-14 16:18 (UTC)

Sorry I've been traveling and out of date on upstream changes. I'll take a look at this over the coming week.

If anybody can confirm @mariow's comments below and that Gist building I might expedite putting that in here.