Package Details: brave-bin 1:1.78.94-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: brave
Last Packager: brave
Votes: 875
Popularity: 20.17
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-05-01 17:04 (UTC)

Dependencies (8)

Required by (9)

Sources (4)

Pinned Comments

brave commented on 2025-04-25 13:00 (UTC)

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 61 Next › Last »

alosarjos commented on 2022-01-10 20:39 (UTC)

@jordangarrison I saw recently that Arch chromium package got rebuilt with some patch to fix it.

In my case is working without any issue. The patches mention X11, so maybe it's working for me because I'm using Ozone/Wayland. Anyways, seems to be an upstream chromium issue.

Thanks for posting the issue on GitHub, sadly it looks like it hasn't been backported to current Chromium version and I don't think Brave will apply it. So you can either:

  1. Enable Ozone Wayland
  2. Install the previous version (If you don't know how I can help you with that)
  3. Install maybe the nightly or brave (Not -bin) version with the patches applied I would say.

Anyways, the users of this package are awesome and they usually notify me really quick of new updates in case I miss them, so if Chromium fixes it, and Brave releases a new update based on fixed Chromium I will update the package ASAP.

jordangarrison commented on 2022-01-10 20:30 (UTC) (edited on 2022-01-10 20:31 (UTC) by jordangarrison)

There is a functionality-breaking issue with the current version of the package which prevents the user from being able to drag and drop into the browser window or rearrange tabs with the mouse. You can follow this issue here (GitHub brave/brave-browser issue #20386).

The previous version of the package does not contain this issue.

Th30 commented on 2022-01-10 00:53 (UTC)

@jemadux: Yes, if you activate them.

jemadux commented on 2021-12-18 14:22 (UTC)

does brave-bin provide brave ads ?

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.

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).

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 61 Next › Last »