I'm quoting James Henstridge on a possible approach to tackle the problem: « The design of the native messaging system for extensions is something that could theoretically fit into a confinement system like snapd or flatpak. Instead of executing the native messaging server directly, the browser could ask something outside the sandbox to execute the server and hand it the communication pipes.
That's quite a large project though: it'd require modifications to the browser(s), design and implementation of an API (maybe in xdg-desktop- portal?), evaluation of the security implications, etc. » -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
