Package Details: brave-bin 1:1.73.91-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: 821
Popularity: 17.69
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2024-11-20 18:19 (UTC)

Dependencies (8)

Required by (10)

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

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 59 Next › Last »

alosarjos commented on 2021-07-29 09:53 (UTC)

Looks like the fix could arrive at Chrome next week. If that happens let's hope Brave makes a new release rebased on it.

alerque commented on 2021-07-29 08:57 (UTC)

I've just tested 1.27.109 and the situation has not improved. With systemd-resolved in the mix it freezes up hard on startup with an error about not being able to reach the update check site. If I disable systemd-resolved and just use the glibc resolver it works fine.

I'm on the fence as to whether to bump this or not until that is fixed. It's clearly an upstream bug and only affects a subset of users, but I think given how common it is its probably not a good idea to force this through yet. Users that want it can bump the version easily enough themselves since no packaging changes are require other than a version bump and skipping the checksum.

alerque commented on 2021-07-29 07:03 (UTC)

@Th30 What DNS resolver is your system using?

Th30 commented on 2021-07-29 01:44 (UTC)

No problems either in my case using v1.27.109

duhdugg commented on 2021-07-28 20:48 (UTC)

@alosarjos No issues with font rendering.

alosarjos commented on 2021-07-28 15:45 (UTC) (edited on 2021-07-28 16:03 (UTC) by alosarjos)

@duhdugg You don't have any problems with text rendering neither? there is an issue with glibc:

https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

Witch the patches applied to the Arch Chromium build (I think these have not been merged yet and then backported to M92)

PD: Latest version is also available on flathub-beta and work nicely with resolved

alosarjos commented on 2021-07-28 06:39 (UTC)

There seems to be a new release based on a new Chromium version but I can't test it right now. I would wait for the regular chromium update to see if it's still requiring the workarounds

duhdugg commented on 2021-07-28 05:32 (UTC)

The pinned comment is inaccurate. The affected chromium code is broken only on systems using systemd-resolved for name resolution. You can use NetworkManager, dhclient, or dhcpcd with systemd-resolved disabled and not be affected by this bug.

Here's a PKGBUILD for the recently-released v1.27.109 if anyone not using systemd-resolved wants to stay updated until this is sorted out: https://gist.github.com/duhdugg/3cb48d09b5f3c31adbc06c55efb466c8

alerque commented on 2021-07-26 08:51 (UTC) (edited on 2021-07-29 08:57 (UTC) by alerque)

1.27.108 is known to be broken on Linux for all users using systemd-resolved. Since this is the default on Arch that would make this broken by default, so we won't be pushing it up here until there is another release that addresses the issue. Those wishing to run a newer release using a different resolver can easily do so by bumping the version to 1.27.109 themselves (see other comments).

alerque commented on 2021-07-24 21:31 (UTC) (edited on 2021-07-30 14:54 (UTC) by alerque)

@jorgicio @francoism90 @CReimer @HOuadhour Please see comments below, comments in the PKGBUILD, and commit history. 1.27.108 is known to be broken on Linux, we won't be pushing it up here until there is a fix.

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 59 Next › Last »