Package Details: brave-bin 1:1.74.51-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: 840
Popularity: 19.45
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-01-29 17:53 (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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 59 Next › Last »

finoderi commented on 2023-05-05 16:00 (UTC)

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.

Vernox commented on 2023-05-05 12:03 (UTC)

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.

finoderi commented on 2023-05-04 18:32 (UTC)

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.

df8oe commented on 2023-05-04 17:29 (UTC)

@NGr: Thanks - I will give it a try :)

NGr commented on 2023-05-04 17:25 (UTC)

@df8oe Once you have cleared the sync data, if you put your sync code back in you shouldn't lose anything.

alosarjos commented on 2023-05-04 17:22 (UTC)

@df8e No problem, I rather have some info here for other users, since I don't use KDE

df8oe commented on 2023-05-04 17:19 (UTC)

@NGr: Does that mean that complete stored passwords are lost after disabling/clearing/starting sync?
@alosarjos: It seems the issue is caused by other packages. I am using machines with testing-repositories and some with stable. All machines with testing repos show the issue, all stable are working up to 1.52. Sorry for the dust!

NGr commented on 2023-05-04 16:51 (UTC)

@df8oe I had the same issue and fixed it with the instructions from here: https://community.brave.com/t/sync-failing-on-ubuntu-22-04-cannot-access-safe-storage/432708/2

alosarjos commented on 2023-05-04 16:49 (UTC)

@df8oe I haven't changed nothing regarding how the app is packaged. I suggest you opening a issue on the brave github

df8oe commented on 2023-05-04 16:47 (UTC)

Since version 1:1.51.110-1 brave does not talk to KDE passwordmanager (kwallet). It complains about "cannot connect to password manager") and so it is. This affects brave-dev-bin starting with 1.51, too. Downgrade to 1.50 gives working passwordmanagement again. Any ideas what can be changed?

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 59 Next › Last »