Package Details: brave-bin 1:1.65.114-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: 761
Popularity: 14.11
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2024-04-17 19:28 (UTC)

Dependencies (8)

Required by (6)

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

1 2 3 4 5 6 .. 56 Next › Last »

zeroskyx commented on 2024-04-18 18:42 (UTC)

Problem with Wayland can be fixed by creating a file ~/.config/brave-flags.conf with content --ozone-platform=wayland -- refer to https://github.com/flathub/com.brave.Browser/issues/576

rabin commented on 2024-04-18 06:00 (UTC)

Version 1:1.65.114-1 does not launch on Wayland on KDE 6 either. As @mcury said, keeping the preferred Ozone platform as X11 in the chrome flags works.

sol2070 commented on 2024-04-17 23:25 (UTC)

Same for me. Version 1:1.65.114-1 does not launch on Wayland (on Gnome). But it launches with the flag --no-experiments .

alosarjos commented on 2024-04-17 20:40 (UTC)

I would recommend opening the browser from a terminal to get some logs and report it on the projects github

mcury commented on 2024-04-17 20:38 (UTC) (edited on 2024-04-17 20:52 (UTC) by mcury)

this last version 1:1.65.114-1 won't launch in my system. Gnome Wayland

Tried to change environments from QT_QPA_PLATFORM=wayland to QT_QPA_PLATFORM="wayland;xcb" but didn't work.

Currently using the flags for wayland in brave. Didn't try to reset the profile. If you remove this flag Preferred Ozone platform - Wayland, it works.

lopdfdfd343 commented on 2024-03-27 21:15 (UTC)

Your site/page for Brave said the last update is today, "Last Updated: 2024-03-27 08:24 (UTC)" & nothing is out of date, but Google released two CVE patches for version 1.64.113, but your download zip file is still pointing to the old March 20th 2024 version. Did you not upgrade it and working on it or pointed to the wrong file for th public?

Neurognostic commented on 2024-03-18 01:36 (UTC) (edited on 2024-03-18 01:36 (UTC) by Neurognostic)

@nfs see the AUR Getting Started section of the wiki. base-devel, which depends on debugedit, is an implicit dependency of all PKGBUILDS.

nfs commented on 2024-03-17 01:02 (UTC) (edited on 2024-03-17 08:16 (UTC) by nfs)

This is the first problem I've had with this package, but When I run $ makepkg -sr on the extracted PKGBUILD, I get:

==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.

I don't know what it's looking for. The dependencies (alsa-lib gtk3 libxss nss ttf-font) are all installed. This only seems to occur when running LXDE.

kronikpillow commented on 2024-03-09 00:51 (UTC)

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

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.

1 2 3 4 5 6 .. 56 Next › Last »