![]() ![]() The number at the end is a session identifier, so strip that and convert underscores ( _) to periods (. We ignore everything up to and including firefox_, giving com_1password_1password_3847301527 If your extension doesn't appear (or is set to no) you can discern the object name from the loglines you looked at above.įor example session /org/freedesktop/portal/desktop/session/1_301/firefox_com_1password_1password_3847301527 You're looking for a yes in the permissions column. Webextensions _browser snap.firefox yes 0x00 If you've other extensions which aren't working, start by checking permissions: flatpak permissions webextensions You can then re-enable the other extensions, and should find KeepassXC continues to work even after you've restarted Firefox. Attempt to connect to KeepassXC: you should now get the prompt to name the browser.go into the browser and temporarily disable the affected/failing extensions.It appears that these failures can impact the initial communication between the browser and KeepassXC. org/freedesktop/portal/desktop/session/1_301/firefox_com_1password_1password_3847301527, unknown handle : D/NativeMessagingPortal cannot close session org/freedesktop/portal/desktop/session/1_301/firefox_com_1password_1password_3847301527 was closed If that's there, look for reported failures for other extensions - on one system I found that 1Password was having issues : D/NativeMessagingPortal session In session /org/freedesktop/portal/desktop/session/1_301/firefox_org_keepassxc_keepassxc_browser_1791972916: Look for lines referring to KeepassXC to see whether communication is successfully being established (linebreaks added for clarity) : D/NativeMessagingPortal got file descriptors for native application To check for this, exit firefox and then run MOZ_LOG=NativeMessagingPortal:5 snap run firefox If you're still not prompted, it may be that other extensions are interfering. It should now work, and Keepassxc will prompt you to provide an identifier for the browser. Run the following sudo apt-get install flatpakįlatpak permission-set webextensions _browser snap.firefox yes ![]() This is because the permissions aren't quite right in the container by default. In the case of KeepassXC you'll probably get The snap should come up with your profile in place, so go to your extension and check whether it can communicate with your password manager/whatever. You should get a prompt asking whether to allow Firefox to launch webextensions: Launch the snap based firefox snap run firefox Kill xdg-desktop-portal to ensure the new version is used systemctl -user restart xdg-desktop-portal Otherwise, install a new snap sudo snap install firefox -beta if there was output above) then switch it over to the beta branch sudo snap refresh firefox -beta If the firefox snap is already installed (i.e. Verify whether you already have a Firefox snap installed snap list | grep "firefox" If you're sporting an older version, trigger an update sudo apt-get update The version you're looking for is 1.14.4-1ubuntu2~22.04.1 (or higher, if you're reading this in the future). deb you can still follow these steps to test the snap support without overly impacting your current install.įirst, you need to ensure that you've got the right version of xdg-desktop-portal: dpkg-query -l | grep "xdg-desktop-portal" If you've already replaced Firefox with a. In this post, I'll run through the process of enabling this communication. There's an updated xdg-desktop-portal which adds support for NativeMessaging, and the beta version of the Firefox snap adds support for communication with local extensions via xdg-desktop-portal. However, if NativeMessaging support is your only concern with snap, the good news is that help is coming. Yesterday, I needed to get things up and running quickly, so looked at how to de- snap my Firefox install. This, amongst other things, is something I previously experienced when Chromium was moved to snap a couple of years ago: Things broke as a result of a lack of support for NativeMessaging in snap, so any extension relying on this mechanism will have issues. My motivation for needing to do this was that the move to snap had broken communication with my password manager ( KeepassXC) and I needed it back up and running in a hurry. Yesterday, I posted documentation detailing how to move Firefox back to using a native package rather than a Snap. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |