| 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: | 820 |
| Popularity: | 16.85 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-11-20 18:19 (UTC) |
@wknapik Thanks for the info. But I'm not sure how should proceed with 2 sources defining the version for the same package (ARM64/X86_64).
As long as they are synced, no problem, but the moment one differs from the other it would trigger unnecessary updates for the other architecture...
@alerque hi. A small update to my previous comment (https://aur.archlinux.org/packages/brave-bin#comment-927259). The overview of versions and the individual version endpoints are now available at a more friendly domain (versions.brave.com). This applies to the overview at https://versions.brave.com/ and the individual endpoints, like https://versions.brave.com/latest/release-linux-x64.version.
@alerque hi. The comment in the PKGBUILD seems to indicate that https://brave-browser-downloads.s3.brave.com/latest/release.version is used to track the latest version. Please use the Linux x64 (https://brave-browser-downloads.s3.brave.com/latest/release-linux-x64.version) and Linux arm64 (https://brave-browser-downloads.s3.brave.com/latest/release-linux-arm64.version) specific endpoints instead. You can also find a human-readable overview at https://brave-browser-downloads.s3.brave.com/. Thanks!
1:1.52.117-1 seems to be working fine with KDE KWallet. Yay!
The problem seems not to be a Brave problem, it is an upstream Chromium issue:
https://community.brave.com/t/notice-unexplained-data-loss-issue/485498
So the best would be to stock with all Brave and Chromium on a working stage until the issue is fixed!
For those who want to downgrade using Git :
git clone https://aur.archlinux.org/brave-bin.git
cd brave-bin
git reset --hard HEAD~1
makepkg -si
Those who want to downgrade version, you probably have the package of the previous one cached and can run it from there. For those who don't the best I can do is offer a ZIP to run a makepkg from there if you want.
When brave-sync is unavailable there is no access to previously saved cookies and passwords. Of course everything was dropped. Big deal...
But yeah, it would be better to allow people to donwgrade the browser to 1.50.125 version.
The last update should be pulled of the aur. After downgrading brave back to the previous working version, all logins have expired and connections removed.
The problem with brave-sync appeared in 1.51.* It can't be fixed with readding the browser to the sync-chain and it happens on gentoo as well. Brave just can't access its safe storage in KDE wallet for some reason. Most likely it's a Chromium problem again. Yet another fuck up after less than a month from the previous one.
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.