Package Details: brave-bin 1:1.65.133-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: 767
Popularity: 12.41
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2024-05-14 16:32 (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 .. 57 Next › Last »

alosarjos commented on 2024-05-13 15:59 (UTC)

@LinuxSquare Probably your download was corrupted and the sha265 avoided installing a corrupted zip :D

LinuxSquare commented on 2024-05-13 15:58 (UTC) (edited on 2024-05-13 15:59 (UTC) by LinuxSquare)

Hi @OscarJ It seems like something went wrong with my build-process. When building, it failed because it couldn't validate the source. Which lead me to compare the source myself by downloading and checking it manually. Since they were different I commented. However, when re-cloning the package and building it, it seems to be working. No idea what went wrong on my side. So it's all okay :)

OscarJ commented on 2024-05-13 15:49 (UTC)

Hi @LinuxSquare. SHA256 checksum for brave-browser-1.65.132-linux-amd64.zip is b5a5486b983a88c479d09fbd3a1723c8a37b71baa8a0a321d23861bd6443b1f7. What do you mean exactly?

LinuxSquare commented on 2024-05-13 09:59 (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.

edtoml commented on 2024-05-06 15:27 (UTC) (edited on 2024-05-06 15:39 (UTC) by edtoml)

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.

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.

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