[SOLVED] Keepassxc-browser extension in Cheomium-ungoogled

3rensho · 04-24-2024, 05:24 AM

I did a clean new install of -current about two weeks ago and am now sorting out a couple of annoying problems. One is the title subject. I have Eric's Keepassxc package (2.7.7) installed along with the browser extension (1.9.0.3) Everything works fine with Firefox (125.0.2) but I can't get it to find the PW database using Eric's Chromium-Ungoogled (123.0.6312.122). I've tried everything I can find searching the internet but to no avail. I thought it might be the .json file in .config/chromium-ungoogled/NativeMessagingHosts but my last iteration does not find the database. If anyone has this browser version and keepassxc-browser working could you please let me know? My .json file is as entered below -

Code:

{
    "allowed_origins": [
        "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
        "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
   ]
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "/usr/bin/keepassxc-proxy",
    "type": "stdio"
}

If you have it working and your .json file is different can you please let me know? Thanks in advance.

camorri · 04-24-2024, 12:21 PM

I just got this working. I updated keepassxc to 2.7.7 from Alienbob. I read through the .deps, I did not have pcsc.lite installed form Alienbob. I installed that, and all is working now on Slackware 15.0.

To be clear, I have:

Keepassxc-2.7.7
Botan 2.19.3
libminizip 1.2.11
pcsc-lite 1.9.5

all on Chromium Version 123.0.6312.122
KeePassXC-Browser 1.8.9

Hope this helps.

gegechris99 · 04-24-2024, 12:39 PM

I have same configuration on Slackware 64bit current:
- keepassxc 2.7.7
- chromium-ungoogled 123.0.6312.122
- keepassxc extension 1.9.0.3

I also have the same json configuration file.

It works here.
I remember that, at some point in the past the keepassxc extension stopped to work, I had to delete the database connection and reconnect (see the extension parameter settings).

Hope this helps.

3rensho · 04-25-2024, 12:03 AM

Thank you for your responses camorri and gegechris99. I had all the deps installed, the browser integration enabled in Keepassxc. Will keep looking for a fix but probably change over to FF as it works.

pan64 · 04-25-2024, 01:56 AM

for*me it was a simple typo, FF could not find that proxy. Probably you need to check if it is really there and the location is really correct (and is really executable).

3rensho · 04-25-2024, 03:33 AM

Just had a look in the extension info under dev tools and found the following -

Code:

Unchecked runtime.lastError: Cannot create item with duplicate id fill_username_password
Unchecked runtime.lastError: Cannot create item with duplicate id fill_password
Unchecked runtime.lastError: Cannot create item with duplicate id fill_totp
Unchecked runtime.lastError: Cannot create item with duplicate id fill_attribute
Unchecked runtime.lastError: Cannot create item with duplicate id show_password_generator
Unchecked runtime.lastError: Cannot create item with duplicate id save_credentials
Unchecked runtime.lastError: Cannot create item with duplicate id request_autotype
page.js:128 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'clearCredentialsTimeout')
    at Object.switchTab (page.js:128:22)
    at init.js:31:14
client.js:383 KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser
global.js:132 [Error client.js:403] KeePassXC-Browser - Failed to connect: Specified native messaging host not found.
global.js:132 [Error keepass.js:941] KeePassXC-Browser - No content script available for this tab.
global.js:132 [Error keepass.js:313] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.
2global.js:132 [Error keepass.js:941] KeePassXC-Browser - No content script available for this tab.
4global.js:132 [Error page.js:132] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.
global.js:132 [Error keepass.js:313] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.
global.js:132 [Error page.js:132] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.

3rensho · 04-25-2024, 04:51 AM

Found some old backup files and replaced the .json file and now everything works.