The package file along with the zip file is deleted on sudo time out, so the same zip needs to be downloaded again and makepkg again Cleanup should be made only after successful install
Search Criteria
Package Details: brave-bin 1:1.65.126-1
Package Actions
| 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: | 766 |
| Popularity: | 14.34 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-05-02 13:07 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libxss
- nss (nss-hgAUR)
- ttf-font (neuropol-ttfAUR, ttf-win7-fontsAUR, ttf-ms-win8AUR, ttf-ms-win8-arabicAUR, ttf-ms-win8-hebrewAUR, ttf-ms-win8-seaAUR, ttf-ms-win8-indicAUR, ttf-ms-win8-japaneseAUR, ttf-ms-win8-koreanAUR, ttf-ms-win8-zh_cnAUR, ttf-ms-win8-zh_twAUR, ttf-ms-win8-thaiAUR, ttf-ms-win8-otherAUR, ttf-noto-fonts-simpleAUR, ttf-kidsAUR, ttf-liberation-sans-narrowAUR, ttf-cavafy-scriptAUR, ttf-ms-fontsAUR, ttf-dejavu-ibAUR, ttf-zeldaAUR, ttf-oxygenAUR, ttf-oxygen-gfAUR, ttf-share-gfAUR, ttf-gostAUR, otf-inconsolata-dzAUR, ttf-d2codingAUR, ttf-ibm-plex-mono-gitAUR, ttf-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, ttf-karlaAUR, ttf-ms-win10AUR, ttf-ms-win10-japaneseAUR, ttf-ms-win10-koreanAUR, ttf-ms-win10-seaAUR, ttf-ms-win10-thaiAUR, ttf-ms-win10-zh_cnAUR, ttf-ms-win10-zh_twAUR, ttf-ms-win10-otherAUR, ttf-win10AUR, ttf-ms-win10-autoAUR, ttf-ms-win10-cdnAUR, noto-fonts-variable-liteAUR, ttf-bmonoAUR, ttf-pt-astra-factAUR, ttf-weblysleekuiAUR, ttf-pt-astra-sansAUR, ttf-pt-astra-serifAUR, ttf-pt-sansAUR, ttf-pt-serifAUR, ttf-pt-monoAUR, ttf-pt-root_uiAUR, ttf-plemoljpAUR, ttf-juiseeAUR, ttf-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, ttf-ms-win11-autoAUR, ttf-ms-win11AUR, ttf-ms-win11-japaneseAUR, ttf-ms-win11-koreanAUR, ttf-ms-win11-seaAUR, ttf-ms-win11-thaiAUR, ttf-ms-win11-zh_cnAUR, ttf-ms-win11-zh_twAUR, ttf-ms-win11-otherAUR, ttf-plemoljp-binAUR, apple-fontsAUR, ttf-dejavu-emojilessAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-liberation, ttf-mona-sans)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (6)
- brave-extension-bitwarden-git (requires brave)
- ice-ssb-git (requires brave) (optional)
- mermaid-cli-brave (requires brave)
- mermaid-cli-brave (requires brave) (make)
- nfauthenticationkey (requires brave) (optional)
- profile-sync-daemon-brave (requires brave) (optional)
Sources (4)
gr523 commented on 2022-01-25 11:21 (UTC)
jordangarrison commented on 2022-01-10 21:00 (UTC)
@alosarjos thanks for the response! I'm using X11 for my setup for stability reasons and have already installed the previous version. I wanted to share this issue on here since it was breaking some expected browser functionality. Unfortunately, this appears to also affect the Beta and Nightly builds of the browser as well.
Y'all are doing great with this, thanks for supporting this browser's availability on Arch! I'll look forward to the patch update!
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:
- Enable Ozone Wayland
- Install the previous version (If you don't know how I can help you with that)
- 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
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.