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: 823
Popularity: 20.30
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 .. 14 15 16 17 18 19 20 21 22 23 24 .. 59 Next › Last »

Nu4425 commented on 2021-11-10 18:05 (UTC) (edited on 2021-11-10 18:08 (UTC) by Nu4425)

@alosarjos Thank you. Also, if I am not mistaken, the Brave's pgp fingerprint can be listed from their official public key with gpg by:

gpg --show-keys BRAVE_PGP_PUBLIC_KEY

If that is the case, then according to the wiki the fingerprint can be supplied to validpgpkeys in PKGBUILD...

alosarjos commented on 2021-11-10 05:27 (UTC)

@Nu4425 I will try to give it a look on how all that works when I get some more free time, for now I just updated the packag :P

Nu4425 commented on 2021-11-08 21:58 (UTC)

Hi @alosarjos, the package builds fine but as an improvement can you verify the authenticity/integrity of the release using brave's official signing key during the build process? This would be great, as Brave provides official signing keys in their website at "https://brave.com/signing-keys/#release-channel".

mdedetrich commented on 2021-10-30 09:40 (UTC)

So I just fixed it, read the archwiki for chromium and updating the flags to brave --use-gl=desktop --enable-features=VaapiVideoDecoder --disable-features=UseOzonePlatform %U seems to have worked (using X11 not Wayland).

mdedetrich commented on 2021-10-30 09:35 (UTC)

Actually ignore my last message, removing --use-gl=egl --enable-features=VaapiVideoDecoder %U did end up working (of course the issue is that I now don't have video video acceleration).

alosarjos commented on 2021-10-30 09:33 (UTC)

Can't help you there more. I'm on Wayland, so no Video Acceleration for me, I'm using EGL flag too though, but it's working fine on my end. AMDGPU here.

If Chromium has the issue closed, maybe it's something on the mesa side for your hardware?

mdedetrich commented on 2021-10-30 09:29 (UTC)

Still get the same issue, I am pretty sure I am hitting https://bugs.chromium.org/p/chromium/issues/detail?id=951142

alosarjos commented on 2021-10-30 05:08 (UTC)

Could you try removing them?

mdedetrich commented on 2021-10-28 09:11 (UTC)

I am using the following flags (for video acceleration) brave --use-gl=egl --enable-features=VaapiVideoDecoder %U

alosarjos commented on 2021-10-22 17:48 (UTC)

@mdedetrich Google Maps is working fine here. Are you using any custom flags?