Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: brave 0.13.1-1

Git Clone URL: (read-only)
Package Base: brave
Description: Web browser that blocks ads and trackers by default.
Upstream URL:
Licenses: custom
Provides: brave-browser
Submitter: mischka
Maintainer: mischka (vorbote)
Last Packager: vorbote
Votes: 30
Popularity: 3.022707
First Submitted: 2016-01-29 19:47
Last Updated: 2017-02-01 12:47

Latest Comments

1 2 3 4 Next › Last »

vorbote commented on 2016-12-06 21:24

Yes, it is broken with the tooling available in Arch. Switch to brave-bin or brave-git for the time being.

Timothee commented on 2016-12-04 15:34

Hi, I have a problem for update brave :

npm ERR! Linux 4.8.11-1-ARCH
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v7.2.0
npm ERR! npm v4.0.3

npm ERR! abp-filter-parser-cpp@1.2.10 preinstall: `npm install bloom-filter-cpp && npm install hashset-cpp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the abp-filter-parser-cpp@1.2.10 preinstall script 'npm install bloom-filter-cpp && npm install hashset-cpp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the abp-filter-parser-cpp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm install bloom-filter-cpp && npm install hashset-cpp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs abp-filter-parser-cpp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls abp-filter-parser-cpp
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/yaourt-tmp-timothee/aur-brave/src/browser-laptop-0.12.11dev/npm-debug.log

Can you help me ? Thanks for your work :)

vorbote commented on 2016-09-21 16:50

The latest nodejs to hit the repos produces fully functional binaries. Enjoy!

vorbote commented on 2016-09-01 19:10

It seems there is a problem with the npm version in the repo. Please stick to the binary releases for now (you are welcome to hack your private PKGBUILD to use an older npm).

vorbote commented on 2016-09-01 17:43

I'm testing 0.11.6dev before pushing it as I write this. Did anyone get around to report this bug upstream?---I tend to use the upstream binary instead of compiling it myself these days.

chipmunkboogie commented on 2016-09-01 17:15

Package stops building:
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
[ .....] \ extract:xml2js: sill doParallel extract 1436

Kasperos commented on 2016-08-31 23:50

Had it stuck in the same spot, running for ~1h. CPU usage on one core was constantly 100%.

ukbeast commented on 2016-08-31 18:37

Does it hang for anyone else at - extract:xml2js: sill doParallel extract 1436?

vorbote commented on 2016-08-25 15:33

We can take care of packaging bugs and perhaps some serious bugs in between releases that have patches released upstream.

Everything else must be reported to the upstream bug tracker, where it belongs.

I feel I must mention, saffronsnail, that brave is pre-alpha quality software in active development. To trust it for anything more than a toy for testing features and helping upstream iron out the bugs, can lead to losing data and serious hair loss.

saffronsnail commented on 2016-08-24 18:53


I'm not 100% sure if this is an issue that should be reported to you or upstream, but I think I'm should report it to you because I don't experience this issue when I use Brave on my Windows installation.

Sometimes when I hit a special character into a text box, such as an @ or a space, that page freezes. It won't respond to any buttons, scroll, etc. All the other tabs continue working fine, and if I close that tab and re-open the page, everything works fine again. I have no clue why this would happen, any assistance you could give me would be appreciated.


EDIT: 'appreciated' has two e's, not two i's