Package Details: brave-bin 1:1.73.91-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: alerque (alosarjos)
Last Packager: alosarjos
Votes: 821
Popularity: 17.69
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2024-11-20 18:19 (UTC)

Dependencies (8)

Required by (10)

Sources (4)

Pinned Comments

alerque commented on 2021-11-27 03:11 (UTC)

@ant0n et all, lets keep the comments here about packaging issues, general Brave usage issues should go in another forum to not clutter up this comment space. I'm deleting comments that have no relation to packaging. Grey areas like crashes that could be blamed on Arch can stay until proven otherwise, but things like how to configure Brave to handle popups or site X or whatever just don't belong here. Thanks for understanding.

Latest Comments

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 59 Next › Last »

core_contingency commented on 2020-04-03 01:04 (UTC)

Thank you for maintaining this! I am always surprised by how quickly you update this package, and it is really nice to have an Arch package for Brave.

francoism90 commented on 2020-04-02 07:30 (UTC)

@mixedCase I don't think upstream will solve this as it depends on mesa and other stuff as well.

mixedCase commented on 2020-04-01 20:24 (UTC)

@francoism90 This PKGBUILD packages the official Brave release. Let upstream know about this in either an existing GitHub issue or a new one.

@monson This PGKBUILD makes a system package owned by Pacman, matching Arch's official Chromium distribution and compliant to FHS 3.0, it's funny you ask because I actually got an e-mail about this around a couple of weeks ago.

Anyway my interpretation of the FHS and what Arch does is that /opt is more for the sysadmin dumping programs that don't follow the system hierarchy and the files aren't owned by the package manager. Although sometimes packagers can't (or can't be arsed to) reorganize everything so they make packages that dump everything to /opt.

monson commented on 2020-04-01 07:44 (UTC)

Since it is a stand-alone binary application provided by commercial company, would it be better if put into /opt/brave instead of /usr/lib/brave-bin?

francoism90 commented on 2020-04-01 07:30 (UTC) (edited on 2020-04-01 07:31 (UTC) by francoism90)

@mixedCase Could you please add the following patch from chromium-vaapi but based on Brave?

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chromium-vaapi#n35 https://aur.archlinux.org/cgit/aur.git/tree/chromium-drirc-disable-10bpc-color-configs.conf?h=chromium-vaapi

It is possible to enable VA-API in Brave, but the color corruptions keep happening.

AlphaPepe commented on 2020-02-26 05:08 (UTC)

Thanks for this. The community package is always out of date. Works great!

mixedCase commented on 2020-02-10 22:40 (UTC)

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 (UTC) (edited on 2020-02-09 10:11 (UTC) by Krzychu)

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

Here's terminal output:

[9789:9789:0209/100534.337651:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

9794:9806:0209/100538.984279:ERROR:broker_posix.cc(40)] 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: https://community.brave.com/t/repeated-crashes-on-1-3-113-on-mac-and-ubuntu/106020/18

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 (UTC)

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/112034.477829:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [2847:2851:0208/112035.636714:ERROR:broker_posix.cc(40)] 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

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 59 Next › Last »