does, asking a brave-vaapi-wayland sound like a reasonable comment @alerque? I recently realized that there is no hardware acceleration in Brave under Wayland, while using ozone platform wayland ... only X11 ... which i was surprised by, as ... to no knowledge of mine, for past 3-4 months i'v been successfully using brave with hardware acceleration on Arch, under prasanthagan's hyprdots, without feeling effected by the bug, as I game trough my browser ... yesterday i switched to Plasma 6, and realized the last version of brave that had Wayland vaapi support was v 1.60.125 ... it still works on that version, the issue there is ... it has a warning in the top right corner that it needs a update :-/ I'v been trying to patch it myself, but unsucessfull ... never patched my own package before
Search Criteria
Package Details: brave-bin 1:1.73.91-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: | 822 |
Popularity: | 17.93 |
First Submitted: | 2016-04-06 13:16 (UTC) |
Last Updated: | 2024-11-20 18:19 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- 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-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-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, 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-cdnAUR, 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-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, ttf-plemoljp-binAUR, ttf-dejavu-emojilessAUR, noto-fonts-variable-liteAUR, ttf-lucida-fontsAUR, ttf-plemoljpAUR, ttf-juiseeAUR, ttf-ms-win10-autoAUR, ttf-karlaAUR, noto-fonts-latin-greek-cyrillicAUR, apple-fontsAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, 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-ms-win11-autoAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-input-nerd, ttf-liberation)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (10)
- brave-extension-bitwarden-git (requires brave) (optional)
- chromium-material-icons-for-github-bin (requires brave) (optional)
- chromium-vencord (requires brave) (optional)
- chromium-vencord-bin (requires brave) (optional)
- chromium-vencord-git (requires brave) (optional)
- 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)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 59 Next › Last »
kronikpillow commented on 2024-03-09 00:51 (UTC)
oriba commented on 2024-02-19 02:54 (UTC)
It would be nice to test the package not only with pulling and building again, but also with cloning freshly and then building. This way everything is fresh and no untracked files ensure success, while packing from fresh repositories might not work.
alosarjos commented on 2024-02-17 21:57 (UTC)
Wont update until it's marked as final release
gothmog123 commented on 2024-02-07 10:24 (UTC)
hi, I'm sosorry to put this here but on a vega AMD gpu video playback microstutters in brave-bin. i don't get that from any other chromium browser
n43 commented on 2024-01-30 04:27 (UTC)
hi, all i got an issue since some weeks on my arch with gnome 45 brave is starting but is stuck beetween 2 workspace i see it when i press win + alt +up like on the img i have share but it dont was on workspace when i go back, someone have got this issue too or can guive me a path to try to get it back? this issue apper like 1 month ago after a system upgrade, regards
mohammedjabbar commented on 2024-01-29 07:17 (UTC) (edited on 2024-01-29 07:33 (UTC) by mohammedjabbar)
Consider adding an option to relocate the vertical tabs to the right. It would be nice to move the vertical tabs panel to the right. Thanks!
oriba commented on 2024-01-26 01:52 (UTC) (edited on 2024-01-26 01:56 (UTC) by oriba)
==> Making package: brave-bin 1:1.61.120-1 (Fr 26 Jan 2024 02:51:26 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> ERROR: brave-bin.sh was not found in the build directory and is not a URL.
@alosarjos: there is no reason why this should just be on my side.
alosarjos commented on 2024-01-18 20:05 (UTC)
@oriba Seems an issue on your end, working fine here
oriba commented on 2024-01-18 19:44 (UTC)
I get "ERROR: brave-bin.sh was not found in the build directory and is not a URL."
alosarjos commented on 2024-01-10 20:27 (UTC) (edited on 2024-01-10 20:28 (UTC) by alosarjos)
@wknapik versions.brave.com is still pointing to 1.61.114
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.