Does GNOME Shell integration extension works with Flatpak Chromium or Ungoogled Chromium?

I find it odd because these work:

And they Flatpaks

Am I missing secret sause? To make it work :slightly_frowning_face:

Using Ungoogled Chromium/Chromium Manjaro latest stable Gnome 47

If I understand your question right:
You are using the Flatpak of Ungoogled Chromium? Or are you using Ungoogled Chromium using a different kind of distribution method?

Anyways, the extenions apps use a dbus-API to connect to the shell for extension management. I don’t know if the browser extensions use the same though or some older method.

Under the assumption you’re using a Ungoogled Chromium with Flatpak and that the browser extensions uses the same dbus-API, you could try the following:

flatpak run --talk-name=org.gnome.Shell.Extensions --talk-name=org.gnome.SessionManager io.github.ungoogled_software.ungoogled_chromium

If the browser extension then works, you could make that permanent with flatpak override or Flatseal.

Changed the title for better clarity. Yes, you got it right. I’m not connecting
Tried the cmd and added to Fkatseal but neither worked.

is this how’s supposed to be add in with Flatseal?

Thank you so much for the time and support!

If the --talk-name addition would’ve worked, it would have been added only at the “Session Bus” category.

Well, using the dbus API was under the assumption the browser extension would use the same APIs as the apps.

Turns out that the browser extension uses an additional software on the system, named gnome-browser-connector. Also, the mechanism it uses would require an additional portal for web extensions, which is discussed, but not available yet.

So, for now you probably need to use the apps instead.

1 Like

Thank you!

It would be nice for the website or the extension to warn the user that Flatpak browsers are not supported at the moment.