Arch Linux User Repository

Here's what I see. Note that --incognito is passed along correctly.

~ cat .config/brave-beta-flags.conf
--incognito

~ brave-beta & 
 %  ~  [7651:7651:0323/083052.822561:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
[7696:7696:0323/083057.229774:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

~ ps aux | grep brave | grep inco
gwhite      7641  0.0  0.0   7520  3640 pts/0    S    08:30   0:00 /bin/bash /opt/brave.com/brave-beta/brave-browser --incognito --disable-gpu-driver-bug-workarounds
gwhite      7651  9.7  0.5 34504444 348140 pts/0 S<l  08:30   0:00 /opt/brave.com/brave-beta/brave --incognito --disable-gpu-driver-bug-workarounds 
[7696:7696:0323/083112.487062:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[7696:7696:0323/083112.495989:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

 ~  cat (which brave-beta)
#!/usr/bin/env bash
XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}"

# Allow users to override command-line options
USER_FLAGS_FILE="$XDG_CONFIG_HOME/brave-beta-flags.conf"
if [[ -f $USER_FLAGS_FILE ]]; then
   USER_FLAGS="$(cat $USER_FLAGS_FILE | sed 's/#.*//')"
fi

if [[ -z "${CHROME_USER_DATA_DIR}" ]]; then
    export CHROME_USER_DATA_DIR=~/.config/BraveSoftware/Brave-Browser-Beta
fi
exec "/opt/brave.com/brave-beta/brave-browser" "$USER_FLAGS" "$BRAVE_FLAGS" "$FLAG" "$@"

The brave-beta-bin.sh script shouldn't have $USER_FLAGS in quotes. In it's current state, the brave-beta-flags.conf file does nothing (test with --incognito for example).

Here is the modified last line that works for me:

exec "/opt/brave.com/brave-beta/brave-browser" $USER_FLAGS $BRAVE_FLAGS $FLAG "$@"

That's weird. It's definitely not a dependency of this package (which you can see in the PKGBUILD.) Must be something else going on.

While installing it's asking Telegram as dependency which's not listed here

Just upgraded to the latest iteration of brave beta and the previously reported error is gone... thank you.

I'm not seeing it here, FWIW

I get this when I start brave, not sure if I am the only one:

brave-browser-beta --version /usr/bin/brave-browser-beta: line 48: 368925 Segmentation fault "$HERE/brave" "$@"

( I am on x64 )

Yes, the solution is to split this into two packages, one for intel and one for arm, until such time as AUR supports this kind of split packaging -or- upstream builds. That would mean dropping arm support here, and then someone else could create an arm package.

That is getting more and more appealing as I continue to field complaints about arm, when I don't even have a way to test the arm package.

@grebunk I'm not sure how well this would work, but here's an idea. Let's say there's a version available for both x64 and arm64, then Brave releases another version, which can be available for either x64 and arm64, or just x64, or just arm64. In the first case, everything would work as it does now. In the second and third, the PKGBUILD would be updated to only contain the one architecture available.

Now that I've written it down, I realize that at least new installations for the missing architecture probably wouldn't work (?), not sure about update behavior.

It would be good to get some advice from the distro/AUR folks - this can't be the first package with this problem.

The obvious solution that comes to mind would be for AUR to support pkgver split by architecture, the way other parameters can be split (source, shasums).

Not that I can see. Right now, the best option seems to be to remove support and let someone who actually has an ARM device to test this with create a new one. At some point, one assumes that upstream will build consistently, but right now it basically an annoyance.