Conflict between brave flatpak and rpm (from official website)

Ask Fedora
1

i have install brave from flathub and official website

sudo dnf install dnf-plugins-core

sudo dnf config-manager --add-repo https://brave-browser-rpm-release.s3.brave.com/x86_64/

sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc

sudo dnf install brave-browser

now if i open rpm one i can’t open flatpak one everytime i tap on it opens rpm one again and again and after closeing all brave i can open flatpak one now i cant open rpm one burt both browser name and version is different as of now. having both is conflicting which should not happen. can other confirm this

2

Collect more information please, logs or messages.

Start Brave-rpm, then start Brave-flatpak using flatpak run com.brave.Browser. What does it say?

Then, close all. Start Brave-flatpak and then start Brave-rpm from command line. What does it say?

1 Like
3

I am not sure I would ever want to run the same app, provided from 2 different sources and potentially with 2 different versions, at the same time. There seems a lot of risk of one interfering with the other somewhere behind the scenes when run that way.

1 Like
4

This is because of how the OS prioritizes by the path. When you install via RPM the executable is in /usr/bin, but the Flatpack is installed in your home directory. It finds the RPM executable before it looks in your home directory.

5

I think that is only true if it is installed with the proper variable preconfigured. This is from the flatpak man page.

ENVIRONMENT
       Besides standard environment variables such as XDG_DATA_DIRS and XDG_DATA_HOME, flatpak is consulting some of its own.

       FLATPAK_USER_DIR
           The location of the per-user installation. If this is not set, $XDG_DATA_HOME/flatpak is used.

       FLATPAK_SYSTEM_DIR
           The location of the default system-wide installation. If this is not set, /var/lib/flatpak is used (unless overridden at build time by
           --localstatedir or --with-system-install-dir).
6

If you used sudo and installed it as root that would matter. If you just run flatpak install whatever or open Software / Discover / whatever software manager and install it that way, it will default to a per-user installation.

On Fedora if you do a user install, you will find your Flatpacks in ${HOME}/.var/app/

7

The default flatpak installation for Fedora flatpak or for Flathub is for system not user. This depends on how the remote is setup not the use of sudo.
IE …
sudo flatpak install firefox, will use the system remote if it is defined. If you only have user remotes defined it will error because there are no remote refs found for firefox.
You should be able to see with flatpak remotes

https://src.fedoraproject.org/rpms/flatpak/blob/rawhide/f/flatpak-add-fedora-repos.service
https://flatpak.org/setup/Fedora

@frankjunior here’s what I’m observing:
run brave web browser (rpm)
alt - tab; shows up as brave
super → brave → shows brave (flatpak) and sometimes brave web browser running (dot underneath icon)
trying to run brave (flatpak) switches to the rpm version
trying to run brave web browser (rpm) opens a new instance of brave.
selecting ctrl + enter on brave (flatpak) opens an instance of the brave flatpak.

If I start by running the flatpak version, I’m able to open the rpm version.

edit: It looks like chromium has similiar behavior.

1 Like
8

when i open rpm one and run flatpak it shows a error but after closing that flatpak commend actually work with some error but it opens the browser ultimately

$ flatpak run com.brave.Browser
bwrap: Can't find source path /run/user/1000/.flatpak-helper/pkcs11-flatpak-4068: No such file or directory
$ flatpak run com.brave.Browser
Gtk-Message: 11:14:58.060: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:14:58.060: Failed to load module "pk-gtk-module"
Gtk-Message: 11:14:58.061: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:14:58.061: Failed to load module "pk-gtk-module"
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[52:52:1103/111510.305355:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305511:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305598:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305692:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305776:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305862:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.305951:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306032:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306112:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306211:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306292:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306374:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306454:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306533:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306612:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306699:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306780:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306882:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.306965:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307045:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307133:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307222:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307300:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307384:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307463:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307542:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307620:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307706:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307785:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307865:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.307944:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308022:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308106:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308194:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308276:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308356:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308441:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308520:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308598:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to dma_buf: No such file or directory (2)
[52:52:1103/111510.308679:ERROR:gbm_wrapper.cc(293)] Failed to export buffer to
9

These kinds of errors are why it is always recommended to use only one version of an app. The flatpak release is not necessarily compatible with the rpm version so user beware when using both on the same system.

10

but both should open at leastis it a bug if you can confirm so i will report

11

I do not think that is a bug. I think it is a version mismatch and the flatpak is out of sync with and has different dependencies and version requirements than the up-to-date rpm version.

In fact changes in software, such as changes in versions used, (gtk4 vs gtk5), (python 2 vs python 3), (python 3.6 vs python 10) (among many others) will usually cause these kinds of errors. The errors you are showing indicate gtk errors.

While I do not use firefox regularly, I think that if you dig in a little you will be able to identify the gtk mismatches and recognize that the flatpak is not necessarily up to date. If anything it should be approached as the flatpak needs updated.

12

no both are on same version as brave pushes update in both on same time like i got update in flatpak and also in rpm.

13

it was brave not firefox but i will try with firefox sure to check about.
brave is just chromium better or opensource chrome without google lookinginto browsing history.