Browser integration doesn't respect XDG_CONFIG_HOME

[NikolausDemmel]

I migrated from an Ubuntu 16.04 machine to a new machine with 18.04. KeepassXC is working, and the browser integration for Firefox as well, but for Chrome it is not. It was working before migration.

I've enabled the browser support in the KeepassXC settings and installed the Chrome Extension. Both should be up to date.

If I click on the KeepassXC icon in Chrome it shows:

KeePassXC-Browser has encountered an error:

Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.

If I click "Reload", the error message changes to

Key exchange was not successful.

In the extension settings, under "connected databases", there are no entries, and if I click "Connect", nothing happens. After migration, there were two entries, but since it wasn't working, I have removed them in the meantime.

One thing that is different to the previous machine, is that now I have XDG_CONFIG_HOME set up, and I copied my chrome user profile to the new location. It is now in ~/bionic/.config/google-chrome/Profile 1, whereas before it was in the more default ~/.config/google-chrome/Profile 1. Could that be a reason for the issue? Note that Firefox doesn't respect XDG_CONFIG_HOME and the firefox profile is still under ~/.mozilla like on the old machine.

Debug info

There seem to be no keepassxc related error messages in the JS console (depending on the site I have open no messages at all)
KeePassXC - 2.5.1
KeePassXC-Browser - 1.5.4
Operating system: Linux
Browser: Chrome

[droidmonkey]

Is chrome running as a snap?

[NikolausDemmel]

Thanks for the quick response.

No, should be from apt package:

google-chrome-stable:
  Installed: 79.0.3945.79-1
  Candidate: 79.0.3945.79-1
  Version table:
 *** 79.0.3945.79-1 500
        500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
        100 /var/lib/dpkg/status

[varjolintu]

The NativeMessagingHosts directory should be under the main configuration path of the browser, can you check it out? It's ~/.config/google-chrome/NativeMessagingHosts.

[NikolausDemmel]

It was empty for my new install. As described above, due to the use of XDG_CONFIG_HOME, the path is ~/bionic/.config/google-chrome/NativeMessagingHosts/. I copied the file org.keepassxc.keepassxc_browser.json from the old path, and now I could connect again. KeepassXC is working.

Is that the native KeepassXC application that is supposed to setup this file, or the chrome extension? Looks like this would need a patch to deal with XDG_CONFIG_HOME properly.

But anyway. My immediate issue is solve, thanks!

[varjolintu]

KeePassXC setups the file and currently it doesn't respect XDG_CONFIG_HOME.