| 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) |
Hm, it seems like the sha256sums have changed: When I download the x86_64 version and run a sha256sum, I get: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Instead of: b5a5486b983a88c479d09fbd3a1723c8a37b71baa8a0a321d23861bd6443b1f7
Did Brave change something? Because when I take a look at the diff, the sha256sum indeed got updated.
This is posted as an aid to reduce frustration ('ll delete this when the fix is in).
There is current a bug in chrome/kde/qt? that gets triggered when using wayland and copying text in brave. https://community.brave.com/t/brave-crashes-while-selecting-or-dragging-page-element-on-fedora-kde/545980
It looks like chromium bug: https://issues.chromium.org/issues/336449364
which is caused by a kde (or qt) bug: https://bugs.kde.org/show_bug.cgi?id=482142
in any case, the chromium devs agree it should not stop responding to mouse clicks and have produced a test fix: https://chromium.googlesource.com/chromium/src/+/876fbd5552c8fb9d4889ba0371e4d7e3bfa9af84^!/
Hopefully the fix will get merged by brave, chromium and/or kde/qt fix the missing events soon. Cause its a real PITA.
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
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.
Same for me. Version 1:1.65.114-1 does not launch on Wayland (on Gnome). But it launches with the flag --no-experiments .
I would recommend opening the browser from a terminal to get some logs and report it on the projects github
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.
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?
@nfs see the AUR Getting Started section of the wiki. base-devel, which depends on debugedit, is an implicit dependency of all PKGBUILDS.
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.
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.