Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser extension will not connect. #1883

Closed
TexasTechnician opened this issue Mar 22, 2023 · 2 comments
Closed

Browser extension will not connect. #1883

TexasTechnician opened this issue Mar 22, 2023 · 2 comments

Comments

@TexasTechnician
Copy link

TexasTechnician commented Mar 22, 2023

Expected Behavior

click the browser extensions option to connect to db. db opens and prompts for approval (new setup of new browser and install of keepass).

Current Behavior

I'm running keepassxc browser extension (latest) in firefox v111.0 (installed via snap) on kubuntu 22.10.

I've tried keepassxc via apt, snap and the app image. The snap version was the only one which produced a different result.

The all produce the same problem. When trying to connect (prompt from the browser plugin) keepass pops up. But is locked (even when it was unlocked, the browser extension call is locking the db). And I am unable to connect the db.

The browser plugin only gives the generic error, "Key exchange was not successful".

The config is:

{
    "allowed_extensions": [
        "[email protected]"
    ],
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "/home/txtechnician/Downloads/KeePassXC-2.7.4-x86_64.AppImage",
    "type": "stdio"
}

I decided to try the edge version instead. It worked with no problems.

Possible Solution

Steps to Reproduce (for bugs)

Debug info

KeePassXC - {2.7.4}
KeePassXC-Browser - {1.8.5.1}
Operating system: Linux Kubuntu v 22.10
Browser: Firefox 111.0 Snap

@droidmonkey
Copy link
Member

Checkout other issues please that discuss this very problem. It is with Firefox snap not us.

@droidmonkey droidmonkey closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2023
@varjolintu
Copy link
Member

See the pinned issue: #1426

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants