Package Details: brave-bin 1:1.3.118-1

Git Clone URL: (read-only, click to copy)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release).
Upstream URL:
Keywords: brave browser
Licenses: BSD, MPL2, custom:chromium
Conflicts: brave
Provides: brave, brave-browser
Submitter: vorbote
Maintainer: mixedCase
Last Packager: mixedCase
Votes: 222
Popularity: 15.38
First Submitted: 2016-04-06 13:16
Last Updated: 2020-02-19 18:04

Dependencies (8)

Required by (1)

Sources (4)

Pinned Comments

mixedCase commented on 2019-03-11 13:52

Before reporting the package as out of date, please note that the newer GitHub release you're looking at belongs to the "Release Channel" and isn't marked as prerelease.

I have a cron running that's checking every 30 minutes if there's a new release and sends me an email if so. If you see the release was tagged in the last couple of hours please give it some time before flagging. Thanks.

NOTE: Also please take into account a stable version may be "released" but not marked as ready for a long time.

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 »

mixedCase commented on 2020-02-10 22:40

For those who were having issues: Brave has released version 1.3.115 with sync disabled, which apparently was the cause of the crashes.

Krzychu commented on 2020-02-09 10:10

@mixedCase on 1.3.113 I got similar errors to those reported by Philotomy.

Here's terminal output:

[9789:9789:0209/] InitializeSandbox() called with multiple threads in process gpu-process.

9794:9806:0209/] Recvmsg error: Connection reset by peer (104)

/usr/bin/brave: line 27: 9766 trace/breakpoint trap (core dumped) usr/lib/brave-bin/brave "$@" $SANDBOX_FLAG $PEPPER_FLASH_FLAG $USER_FLAGS

The very first error line can be safely ignored - it's also thrown on 1.3.114. The next two are specific to 1.3.113 and probably are the cause of problems.

I don't think there is much to play with. Especially since it worked perfectly before - since like 1.0.X. It also works great with 1.3.114. Due to this I'm going with 1.3.114 for the moment.

Out of curiosity, I just took a look at brave community - the issues is reported by various Linux and Mac users. Brave recommends to give 1.3.114 a try (they called it a test version). So indeed 1.3.114 is some kind of pre-release. According to this topic 1.3.114 helps for some, but not all. Link:

I have noticed one thing though. On my other device with Windows 10, the installed version of brave is still 1.2.43. Brave auto-updater doesn't find new version. I think it's more of fun fact and it will update to 1.3.X at some point.

Philotomy commented on 2020-02-09 04:15

I'm also seeing the behavior Krzychu reported with 1.3.113 (crash upon launch). Messages are:

error: package 'pepper-flash' was not found mesa: for the --simplifycfg-sink-common option: may only occur zero or one times! mesa: for the --global-isel-abort option: may only occur zero or one times! [2841:2841:0208/] InitializeSandbox() called with multiple threads in process gpu-process. [2847:2851:0208/] Recvmsg error: Connection reset by peer (104) /usr/bin/brave: line 27: 2816 Trace/breakpoint trap (core dumped) /usr/lib/brave-bin/brave "$@" $SANDBOX_FLAG $PEPPER_FLASH_FLAG $USER_FLAGS

mixedCase commented on 2020-02-08 22:31

1.3.113 is currently working fine here on a couple of machines.

1.3.114 is still marked as pre-release (now almost 24 hours after first tagging it) and this package strictly follows upstream so I can't switch to that.

@Krzychu if you could go into detail about the kind of error you see on the terminal when launching Brave 1.3.113 maybe we know if there's something else at play.

Krzychu commented on 2020-02-08 10:06

In my case update to 1.3.113 broke brave - it would crash before letting me open any page. There is already newer version - 1.3.114. I have manually updated brave and it seems like the issue is fixed.

Hope this helps some folks that will also encounter similar problem. Or if you haven't updated yet you might want to wait till maintainer updates package to 1.3.114.

erikdubois commented on 2020-02-03 18:11

You are quite right. I was building the brave build by mistake ... wow never again I will build that - sorry for the confusion and thanks for maintaining the bin version

spsf64 commented on 2020-02-03 11:20

@erikdubois, I believe you are talking about package "brave", not brave-bin??

erikdubois commented on 2020-02-03 09:45

I am currently building brave-bin and it takes as super long time. What I am worried about is the message It is downloading at 90% finished and I have 18GB downloaded - can this be correct?

mixedCase commented on 2020-01-08 19:26

@Yazarai Yeah not sure what that was all about but I was able to reproduce that it will not run after disabling user namespaces.

Honestly? The setuid sandbox will be deprecated upstream and the Brave team seems to want to support it even less so I suggest to just enable them, it's not like no-sandbox will be secure. But I will leave the workaround at least not to annoy current users.

Yazarai commented on 2020-01-08 19:02

@mixedCase Hey again! Apparently I missed something in my report, as now Brave won't even open. I then tried to open from the terminal and this was the output:

[16186:16186:0108/] No usable sandbox! You probably need to enable user namespaces in your kernel. See <> for more information.

/usr/bin/brave: line 22: 16186 Trace/breakpoint trap (core dumped) /usr/lib/brave-bin/brave "$@" $PEPPER_FLASH_FLAG $USER_FLAGS

Really weird considering what upstream said and showed. Could the problem be anything aside from the zip?