Updated How-To for KeepassXC and Firefox for 2nd User

[CmdNorbert]

Just in case someone else is having similar problems when trying to get both flatpaked Firefox and KeepassXC to work:

Enabling the Communication for the first user on the computer just works the same as in the Tutorials by rugk.[1]

When trying to this for another user on the same system, this How-To will fail on Aurora, as KeepassXC-Browser won’t be able to connect to KeepassXC. To make this work again, the org.keepassxc.keepassxc_browser.json File needs to be edited. The path-Parameter needs to be updated, so it doesn’t run in the path /home/... but /var/home/…:

{
    "allowed_extensions": [
        "keepassxc-browser@keepassxc.org"
    ],
    "description": "KeePassXC integration with native messaging support, workaround for flatpaked Firefox, see 
",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "/var/home/REPLACE_WITH_USERNAME/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/keepassxc-proxy",
    "type": "stdio"
}

The reason for this is unclear to me, as /home should just work like bind-mount and work the same on all users.
Afterwards do all the remaining steps the same way as the How-To by rugk says.

Remember, if your second user isn’t an Adminstrator-Account, when Allowing the Firefox Flatpak Access to the socket, to use the command

$ flatpak override --user --filesystem=xdg-run/kpxc_server:ro org.mozilla.firefox

instead (I’m not sure, whether it is needed after all).

[1] [HOW TO] Run Firefox *and* KeePassXC in a flatpak and get the KeePassXC-Browser add-on to work - Flathub Discourse

[klmcw]

For future readers: the reasons why /home is not a direct replacement for /var/home is covered in this thread:

Dropbox support

That is another view of the symptom. The reality is that there is nothing to move! But the code inside of the flatpak: doesn’t understand the metadata it is getting from the composefs fs type is not expecting /home to be a symlink and so is not doing the equiv of performing a stat command the follows the symlink. For example, look at the difference of this output: $ stat /home File: /home -> var/home Size: 8 Blocks: 8 IO Block: 4096 symbolic link Device: 0,39 Inode: …

TL;DR - this is because of the introduction of the composefs overlay for / - and the lack of support for it in various flatpaks, etc. Forcing the app to look at /var/home forces it to examine a fs type for which it does have awareness.

The details are in the linked thread above …