Arch Linux User Repository

@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.

To fix default browser under chrome and to avoid showing the icon two times in the gnome dock, you can create a file ~/.local/share/applications/brave-browser.desktop with the following content:

(the most important line here is the StartupWMClass=brave-browser pointing to the correct window manager class name)

[Desktop Entry]
Version=1.0
Name=Brave Browser
# Only KDE 4 seems to use GenericName, so we reuse the KDE strings.
# From Ubuntu's language-pack-kde-XX-base packages, version 9.04-20090413.
GenericName=Web Browser
GenericName[de]=Web-Browser
# Not translated in KDE, from Epiphany 2.26.1-0ubuntu1.
# Gnome and KDE 3 uses Comment.
Comment=Access the Internet
Comment[de]=Internetzugriff
Exec=/usr/bin/brave %U
StartupNotify=true
StartupWMClass=brave-browser
Terminal=false
Icon=brave
Type=Application
Categories=Network;WebBrowser;
Actions=new-window;new-private-window;
Name[de_DE]=Brave Browser

[Desktop Action new-window]
Name=New Window
Name[de]=Neues Fenster
Exec=/usr/bin/brave

[Desktop Action new-private-window]
Name=New Incognito Window
Name[de]=Neues Inkognito-Fenster
Exec=/usr/bin/brave --incognito
MimeType=x-scheme-handler/unknown;x-scheme-handler/about;text/html;text/xml;application/xhtml_xml;image/webp;x-scheme-handler/http;x-scheme-handler/https;x-scheme-handler/ftp;

And as suggested by @whezzel update ~/.config/mimeapps.list to use brave-browser.desktop for all browser related entries.

@dencrypt Regarding brave shield settings: https://github.com/brave/brave-browser/issues/1150

As @asynec I also have the problem with browser always telling me to set default browser. Tried the Suggestions from @whezzel but no avail unfortunately.

<s>Also the Brave Shield settings (in the address bar) has a UI that lacks any icons or text. It's just the sliders and the name of the page. Hard to set anything when I don't know what it is :) However great work anyway. These are just small complaints tbh and it works otherwise fine!</s>
This is an upstream bug.

I use Cinnamon DE and had similar issues. I was able to fix it by editing ~/.config/mimeapps.list and changing all occurrences of chromium.desktop (my previous browser) to brave-bin.desktop, and deleting all the BraveBrowser data stored in ~/.cache and ~/.config.

I'm not sure why, but brave bugged me, for several days, about setting it to default, but a friend of mine said he only clicked 'Set as Default' once and it stopped asking him.

Any idea why this package always complains that it is not set to the default browser, even when it actually is? Using Gnome, fwiw.

@simonorono Awesome. Thanks for such a quick fix

I just solved that issue on version 0.56.15 @whezzel

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.

@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)

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.