Keepassxc: macOS - Can't connect database + keepassxc-proxy cannot be opened

Created on 3 Jun 2019  路  4Comments  路  Source: keepassxreboot/keepassxc

Expected Behavior

Be able to connect a database and use the extension with the desktop app as intended.

Current Behavior

  1. Each time I open my browser, I get the following error :
    keepassxc-proxy

  2. In the extension's settings, clicking on the button "Connect" the tab "Connected Databases" does nothing.

## Possible Solution
-

Steps to Reproduce

  1. Install the desktop app : brew cask install keepassxc
  2. Install the browser extension (in my case Chromium) : https://chrome.google.com/webstore/detail/keepassxc-browser/oboonakemofpalcgghocfoadofidjkkk
  3. Enable Browser Integration in the desktop app
  4. Open extension's setting and try to connect a database

Context

Before creating this Issue I was using the desktop app v2.4.1 + the browser extension v1.4.4 and everything was working fine.
I just upgraded them to v2.4.2 and v.1.4.6 and I get these errors.

I tried to uninstall/uninstall the extension, close the browser, disable Browser Integration, close the desktop etc. No change.

Debug Info

KeePassXC - Version 2.4.2
Revision: a775031

Qt 5.12.3
Debugging mode is disabled.

Operating system: macOS Mojave (10.14)
CPU architecture: x86_64
Kernel: darwin 18.6.0

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (signed and unsigned sharing)
  • YubiKey
  • TouchID

Cryptographic libraries:

  • libgcrypt 1.8.4
bug distribution macOS

Most helpful comment

Another workaround is to use install_name_tool for fixing the linking:

install_name_tool -change /usr/local/opt/libsodium/lib/libsodium.23.dylib "@executable_path/../Frameworks/libsodium.23.dylib" /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy

All 4 comments

There was a deployment error in our macos build pipeline. The proxy application is looking for libsodium in the wrong directory. You can either downgrade to 2.4.1 or install homebrew (https://brew.sh) then install libsodium using brew install libsodium

We cannot publish a new macOS release until next week. The lead maintainer with the signing key is AFK.

Another workaround is to use install_name_tool for fixing the linking:

install_name_tool -change /usr/local/opt/libsodium/lib/libsodium.23.dylib "@executable_path/../Frameworks/libsodium.23.dylib" /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy

Note that using the name tool will invalidate the app signature and prevent use of touchid. It might also impact Auto-Type

Looks like you have the brew. So brew install libsodium will be okay.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TheZ3ro picture TheZ3ro  路  3Comments

813gan picture 813gan  路  3Comments

clementlesne picture clementlesne  路  3Comments

nfnty picture nfnty  路  3Comments

rugk picture rugk  路  3Comments