Package Details: brave-bin 1:1.25.73-2

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: 412
Popularity: 28.81
First Submitted: 2016-04-06 13:16
Last Updated: 2021-06-17 14:45

Dependencies (8)

Required by (2)

Sources (4)

Pinned Comments

mixedCase commented on 2019-03-11 13:52


Before making your report, 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.

Also please take into account a stable version may be "released" on GitHub but not marked as ready (read, NOT PRELEASE) for a long time.

Another handy tool to check latest OFFICIALLY MARKED AS STABLE version of Brave is to run:


aurelieng commented on 2016-05-21 04:04

@vorbote Thanks, I deleted my profile, and it now works again :)

vorbote commented on 2016-05-20 21:06

@aurelieng try deleting the browser profile ($HOME/.config/brave). It works for me, but I know version 0.9.4 had profile corruption problems.

aurelieng commented on 2016-05-20 06:38

Since a few days, Brave starts with a blank window with the following content instead of its UI:

document.getElementsByTagName('head')[0].appendChild(baseNode) const createScript = function (scriptPath) { return new Promise(function (resolve, reject) { var script = document.createElement('script') script.type = 'text/javascript' script.src = scriptPath script.async = true script.onload = resolve script.onerror = reject document.body.appendChild(script) }) } document.querySelector('#webpackLoading').style.display = 'block' createScript(appEntry).catch(function () { document.querySelector('#webpackLoading').style.display = 'none' document.querySelector('#setupError').style.display = 'block' })

Any idea what could be wrong?

vorbote commented on 2016-04-21 19:43

Official releases only. NO RC candidates here! Feel free to report a formal release but do not report a "PRE (DO NOT DOWNLOAD UNLESS YOU ARE TESTING THIS RELEASE CANDIDATE)" if I've missed it somehow. Very unlikely, as I receive the notifications in almost realtime. Do consider that if I don't update when you want is because I have a life and also need to sleep, in my timezone, not yours.

ondoho commented on 2016-04-05 06:34

the line
ln -s /usr/lib/brave-browser/Brave "$pkgdir"/usr/bin/brave
in PKBUILD should read
ln -s /usr/lib/brave-browser/brave "$pkgdir"/usr/bin/brave

it's a small, but elusive error. caused me much confusion (bave: command not found).

kozaki commented on 2016-03-31 12:26

Latest release builds fine.
Whether me commenting out 'SRCPKGDEST=' in this system makepkg.conf or the '$srcdir/brave.png' new syntax in the PKGBUILD most probably allowing for that.

Be sure I'd review my BUILD environement thoroughly if any other PKGBUILD failed to build, which isn't the case atm (60 packages in two architectures).

vorbote commented on 2016-03-25 01:02

@shuu, I must apologize. Earlier today I was very short on time when I read your email (already leaving for church) and did a very cursory check. Somehow I forgot to update the checksums array. That is fixed now.

vorbote commented on 2016-03-24 22:18

@shuu, that's the correct sha384 checksum against my local git repo, synced with AUR. Try downloading again the pkgbuild files and copying over the upstream binary (no need to waste bandwith if you already have the upstream bundle).

And sorry all for the short list revision dance. fd.o bit me hard this time.

shuu commented on 2016-03-24 19:09

I got '43d5244a193bb093972c070fbc8f79cc59a3b46a034cb028edd2f645437633fd91226c6c36b713d1f387fbc377714f9d' for the sum on brave.desktop. Is this a problem with my package or a mistake?

vorbote commented on 2016-03-14 16:12

@kozaki I do not take it personally but your insistence is obsesive compulsive. I only stated the facts. "Loosing time", by the way? Read <>.

Your claims about a defective PKGBUILD are simply not true. I concede I noticed a couple of stylistic inconsistencies last night and they will be in the next package. But none of those fixes will make an impact in your problem, which apparently is far greater than you suppose. I would presume your system is borked, back up everything, wipe the disk and start over.

As there is a new release, I'll upload it later when I have the time, the new version works great, btw. I've already taken measures to minimized the impact of sysem libraries on the binary package.

Cheers, V.