| 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: | brave |
| Last Packager: | brave |
| Votes: | 887 |
| Popularity: | 18.41 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2025-06-18 17:07 (UTC) |
Just add --password-store=basic to your starting flags to solve all the session issues (stored user being lost on restart/reboot for instance).
Explicitly passing --password-store=basic can cause data loss for users who already used the browser with a different password store.
It also effectively disables encryption.
See: https://github.com/brave/brave-browser/issues/32314 for more info
Just add --password-store=basic to your starting flags to solve all the session issues (stored user being lost on restart/reboot for instance).
@Dingisoul please check out the pinned comment. Bug reports made here will not be seen by the Brave dev team.
Hi, I've found that the Wayland input method doesn't work with the newest Brave browser version. However, it does work on version 1.77.97. Does anyone know why this might be happening?
Please i have git cloned the URL and makepkg -csi but it times out at the download of the zip file. I have also tried installing with 'paru' same thing. What could be the problem? Is the repository of line or what else can I try?
@Stebalien could you please file an issue at https://github.com/brave/brave-browser/issues? The comment section here isn't great for keeping track of what needs to be done and any related discussions. The more info you include, the better. Also, feel free to tag @brave/devops-team for better visibility. We're planning some other improvements to the Brave packages in AUR and what you suggest could be a part of that.
Additionally, you might want to consider removing a few files from the package:
/opt/brave-bin/xdg-* aren't necessary given that arch has up-to-date xdg scripts./opt/$pkgname/brave-browser is redundant with /usr/bin/brave but doesn't apply the user's flags.The current wrapper (brave-bin.sh) is a bit out of date:
CHROME_WRAPPER so PWAs installed through brave don't use the correct wrapper.The following patch should bring it up to date (ignoring features from the upstream wrapper that we don't need like replacing the XDG scripts).
diff --git a/brave-bin.sh b/brave-bin.sh
index 31c435c..5654eb1 100644
--- a/brave-bin.sh
+++ b/brave-bin.sh
@@ -21,5 +21,13 @@ do
done
export CHROME_VERSION_EXTRA='stable'
+export CHROME_WRAPPER="`readlink -f "$0"`"
+export GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME
+
+# Sanitize std{in,out,err} because they'll be shared with untrusted child
+# processes (http://crbug.com/376567).
+exec < /dev/null
+exec > >(exec cat)
+exec 2> >(exec cat >&2)
exec /opt/brave-bin/brave "${FLAG_LIST[@]}" "${@}"
Someone opened an issue for it on github: https://github.com/brave/brave-browser/issues/45171
Pinned Comments
brave commented on 2025-04-25 13:00 (UTC)