Not able to open Brave. Failed to sync with dbus proxy

Ask Fedora
, ,
1

Hi on Secureblue, Brave is installed but doesn’t start. Origin software app.

flatpak run com.brave.Browser
F: X11 socket /tmp/.X11-unix/X0 does not exist in filesystem, trying to use abstract socket instead.
ERROR: ld.so: object ‘/var/run/host/usr/lib64/glibc-hwcaps/x86-64-v3/libhardened_malloc.so’ from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[2:2:0817/115926.630671:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:249] Missing X server or $DISPLAY
[2:2:0817/115926.630701:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

Failed to sync with dbus proxy
Any suggestions?

From terminal flatpak run com.brave.browsers gives me 2 errors:

I tired to give access through flatseal to dbus session bus and dbus system bus but nothing change.

2

@boredsquirrel has a repository here with some advice on this and a script: GitHub - boredsquirrel/browserscript-fedora-atomic: A simple interactive script to install Brave (stable, beta, nightly) or Vivaldi on Fedora Atomic

1 Like
3

Thank you very much, this is a good guideline. By the way, is it so different to download via Flatpak to then change permissions with Flatseal compared to download the app with no sandbox and then add this with Bubblejail?

Not even Bubblejail works on my Securblue but on Silverblue it does, giving me some extra possible changes as the folder where it can have access etc.

4

Questions about secureblue.dev should probably be asked in their communication channels.

1 Like
5

Yes it is fundamentally different. Flatseal cannot change anything relevant here.

This is explained in a different post by me