Package Details: brave-bin 0.57.18-1

Git Clone URL: (read-only)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release).
Upstream URL:
Licenses: custom
Conflicts: brave-bin
Provides: brave-bin, brave-browser
Submitter: vorbote
Maintainer: simonorono
Last Packager: simonorono
Votes: 130
Popularity: 8.057143
First Submitted: 2016-04-06 13:16
Last Updated: 2018-12-08 13:03

Pinned Comments

simonorono commented on 2018-11-15 03:35

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

jamesmurray commented on 2018-12-10 09:43

It shows that it is not set to the default browser, even when it actually is.

joschi127 commented on 2018-12-01 18:23

To fix default browser under chrome and to avoid showing the icon two times in the gnome dock, you can create a file ~/.local/share/applications/brave-browser.desktop with the following content:

(the most important line here is the StartupWMClass=brave-browser pointing to the correct window manager class name)

[Desktop Entry]
Name=Brave Browser
# Only KDE 4 seems to use GenericName, so we reuse the KDE strings.
# From Ubuntu's language-pack-kde-XX-base packages, version 9.04-20090413.
GenericName=Web Browser
# Not translated in KDE, from Epiphany 2.26.1-0ubuntu1.
# Gnome and KDE 3 uses Comment.
Comment=Access the Internet
Exec=/usr/bin/brave %U
Name[de_DE]=Brave Browser

[Desktop Action new-window]
Name=New Window
Name[de]=Neues Fenster

[Desktop Action new-private-window]
Name=New Incognito Window
Name[de]=Neues Inkognito-Fenster
Exec=/usr/bin/brave --incognito

And as suggested by @whezzel update ~/.config/mimeapps.list to use brave-browser.desktop for all browser related entries.

rEnr3n commented on 2018-11-29 02:07

@dencrypt Regarding brave shield settings:

dencrypt commented on 2018-11-28 14:02

As @asynec I also have the problem with browser always telling me to set default browser. Tried the Suggestions from @whezzel but no avail unfortunately.

<s>Also the Brave Shield settings (in the address bar) has a UI that lacks any icons or text. It's just the sliders and the name of the page. Hard to set anything when I don't know what it is :) However great work anyway. These are just small complaints tbh and it works otherwise fine!</s>
This is an upstream bug.

whezzel commented on 2018-11-24 08:44

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.

asynec commented on 2018-11-24 00:48

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

@simonorono Awesome. Thanks for such a quick fix

simonorono commented on 2018-11-23 16:57

I just solved that issue on version 0.56.15 @whezzel

whezzel commented on 2018-11-23 12:14

I understand the reason for the 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 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

@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 checks if you have user namespaces enabled; if not then it will run Brave with the --no-sandbox flag.

This is a known issue:

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

[23868:23868:1117/] No usable sandbox! Update your kernel or see <> 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)