extensions.gnome.org doesn't work about com.google.chrome

[mwleeds]

Possibly because the chrome-gnome-shell package puts things in /etc:

↳ dnf repoquery -l chrome-gnome-shell
Last metadata expiration check: 0:06:33 ago on Tue Jan  4 15:20:48 2022.
/etc/chromium
/etc/chromium/native-messaging-hosts
/etc/chromium/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
/etc/opt/chrome
/etc/opt/chrome/native-messaging-hosts
/etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
/usr/bin/chrome-gnome-shell
/usr/lib/python3.10/site-packages/chrome_gnome_shell-0.0.0-py3.10.egg-info
/usr/lib64/mozilla/native-messaging-hosts
/usr/lib64/mozilla/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
/usr/share/applications/org.gnome.ChromeGnomeShell.desktop
/usr/share/dbus-1/services/org.gnome.ChromeGnomeShell.service
/usr/share/icons/hicolor/128x128/apps/org.gnome.ChromeGnomeShell.png
/usr/share/icons/hicolor/16x16/apps/org.gnome.ChromeGnomeShell.png
/usr/share/icons/hicolor/48x48/apps/org.gnome.ChromeGnomeShell.png
/usr/share/licenses/chrome-gnome-shell
/usr/share/licenses/chrome-gnome-shell/LICENSE

... but the host /etc in the sandbox is mounted at /run/host/etc so maybe Chrome isn't looking there. Just a guess.

[wjt]

@ramcq did you write up your hacks around getting this to work with Flatpak:ed browsers anywhere public?

[refi64]

Possibly because the chrome-gnome-shell package puts things in /etc:

Well more specifically, Chrome's native messaging host lookup paths are hardcoded and can't be changed, and trying to merge them into the user config isn't exactly trivial.

[BurnerWah]

I fiddled around with this a while back on Firefox, and I remember there being a way to use flatpak-spawn --host to run the native messaging host outside of the flatpak.
It's not exactly elegant or ideal, though.

I'll try and figure out how I did that again later.

[encrustace]

Any permanent fix?