| 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: | 822 |
| Popularity: | 18.67 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-11-13 21:57 (UTC) |
1.3.113 is currently working fine here on a couple of machines.
1.3.114 is still marked as pre-release (now almost 24 hours after first tagging it) and this package strictly follows upstream so I can't switch to that.
@Krzychu if you could go into detail about the kind of error you see on the terminal when launching Brave 1.3.113 maybe we know if there's something else at play.
In my case update to 1.3.113 broke brave - it would crash before letting me open any page. There is already newer version - 1.3.114. I have manually updated brave and it seems like the issue is fixed.
Hope this helps some folks that will also encounter similar problem. Or if you haven't updated yet you might want to wait till maintainer updates package to 1.3.114.
You are quite right. I was building the brave build by mistake ... wow never again I will build that - sorry for the confusion and thanks for maintaining the bin version
@erikdubois, I believe you are talking about package "brave", not brave-bin??
I am currently building brave-bin and it takes as super long time. What I am worried about is the message It is downloading at 90% finished and I have 18GB downloaded - can this be correct?
@Yazarai Yeah not sure what that was all about but I was able to reproduce that it will not run after disabling user namespaces.
Honestly? The setuid sandbox will be deprecated upstream and the Brave team seems to want to support it even less so I suggest to just enable them, it's not like no-sandbox will be secure. But I will leave the workaround at least not to annoy current users.
@mixedCase Hey again! Apparently I missed something in my report, as now Brave won't even open. I then tried to open from the terminal and this was the output:
[16186:16186:0108/185601.983661:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! You probably need to enable user namespaces in your kernel. See <https://brave-browser.readthedocs.io/en/latest/installing-brave.html#linux> for more information.
/usr/bin/brave: line 22: 16186 Trace/breakpoint trap (core dumped) /usr/lib/brave-bin/brave "$@" $PEPPER_FLASH_FLAG $USER_FLAGS
Really weird considering what upstream said and showed. Could the problem be anything aside from the zip?
@Yazarai Thanks for the great report! 1.2.42 was just released so I just removed the --no-sandbox workaround. Please let me know if any issues arise in systems without user namespaces.
Dear maintainer,
With the 1.2.41 release, Brave has begun to allow the use of Chromium's sandbox when user namespaces are disabled: https://github.com/brave/brave-browser/issues/6247. This was done partially out of security concerns about user namespaces as a sandbox - see https://github.com/brave/brave-browser/issues/3420 for details.
However, brave-bin.sh still contains a command that makes the browser run with the --no-sandbox flag when namespaces are disabled, which is no longer necessary and makes it impossible to run the other sandbox. Please fix this.
@mixedCase - thanks; that did the trick! I just pulled and did 'pacman -Scc'. (PS AUR helpers are an abomination ;)
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.