Package Details: brave-bin 1:1.75.180-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: brave
Last Packager: brave
Votes: 848
Popularity: 20.49
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-02-21 22:41 (UTC)

Dependencies (8)

Required by (8)

Sources (4)

Pinned Comments

wknapik commented on 2025-02-06 18:10 (UTC)

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 .. 46 47 48 49 50 51 52 53 54 55 56 .. 60 Next › Last »

whezzel commented on 2018-11-23 12:14 (UTC)

I understand the reason for the brave-bin.sh script, is to notify the user that the browser is not running in a sandbox which can be insecure. I have applied the fix listed in the 'pinned' comment so that my browser runs in a sandbox.

My question is, would it be possible to modify brave-bin.sh to pass additional flags to /usr/lib/brave-bin/brave?

For example:

brave --incognito     # opens a new brave window with a url of --incognito

/usr/lib/brave-bin/brave --incognito     # opens a new window in incognito mode.

Unfortunately, I'm not that great with scripting yet, otherwise I would try to make this modification on my own.

simonorono commented on 2018-11-17 19:41 (UTC) (edited on 2018-11-17 19:42 (UTC) by simonorono)

@Vrakfall the main Brave executable gets installed at /usr/lib/brave-bin/brave and will not run unless:

1) it finds a way of sandboxing the processes or 2) it's run with the --no-sandbox flag (very insecure)

The brave-bin.sh checks if you have user namespaces enabled; if not then it will run Brave with the --no-sandbox flag.

This is a known issue: https://github.com/brave/browser-laptop/issues/9955

If you try to run the main Brave executable with no flags you get this:

[23868:23868:1117/153840.810367:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see <https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md> for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap (core dumped)

Vrakfall commented on 2018-11-17 14:34 (UTC)

I can't find which command this flag is from. What is it linked to? I find it weird you advice using a kernel feature that weakens it.

async commented on 2018-11-16 05:56 (UTC)

Looks like there is an error in the desktop file... in Gnome, the desktop file opens a duplicate icon in the dock when added to favorites.

simonorono commented on 2018-11-15 03:35 (UTC) (edited on 2018-11-15 03:35 (UTC) by simonorono)

To disable the message telling "that you're using an unsupported command-line flag --no-sandbox" you must enable user namespaces with sysctl:

sudo sysctl kernel.unprivileged_userns_clone=1

To make it persist after reboot:

echo kernel.unprivileged_userns_clone = 1 | sudo tee /etc/sysctl.d/00-local-userns.conf

alerque commented on 2018-11-14 16:18 (UTC)

Sorry I've been traveling and out of date on upstream changes. I'll take a look at this over the coming week.

If anybody can confirm @mariow's comments below and that Gist building I might expedite putting that in here.

mariow commented on 2018-11-10 20:35 (UTC)

This PKGBUILD works to update brave-bin to the currently latest 0.56.12 for me: https://gist.github.com/mariow/b295c2f0c6dc9f274cdf324873a1d712 For full disclosure: that version either isn't as stable as one would like or there are open issues with dependencies, some UI elements look a bit unfinished.

ronaldscott commented on 2018-11-01 20:25 (UTC)

@veox The old Muon-based Brave browser in the browser-laptop repo that this package sources is no longer considered the mainline Brave browser product and I don't think it qualifies for the 'stable' label. They've created a new Chromium-based browser, available at the brave-browser repo. See https://brave.com/new-brave-browser-release-available-for-general-download/ for more info.

Indeed:

The Muon-based Brave browser is no longer available for download on our site, but users who currently browse with it (latest version is 0.25.2) will continue to receive necessary updates until they are fully upgraded to this new release in the near future.

veox commented on 2018-11-01 20:16 (UTC)

Merely bumping pkgver to 0.25.2 (as well as updating the hash-sums) should be enough for those still wishing to use the "stable" channel.

No need to switch to the beta repo.

tve commented on 2018-11-01 04:15 (UTC)

Thanks for the tip, ronaldscott!

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 54 55 56 .. 60 Next › Last »