-
Notifications
You must be signed in to change notification settings - Fork 26
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
KeePassXC-Browser does not connect with KeePassXC #39
Comments
This issue is probably similar to #34 |
I think here is also another (probably unrelated) bug: Chromium can't connect to KWallet. |
Try using |
This is definitely due to native extension hosts. Kwallet would be a different issue however. |
For reference: flathub/org.keepassxc.KeePassXC#29 When I last worked on something similar for Firefox and KeePassXC (both as flatpaks) all browsers on Flathub lacked the necessary native host extension points. I am happy to see that is no longer the case. One question though: Would it be possible to standardize the native host extension prefix similar to: org.freedesktop.LinuxAudio.BaseExtension. I would love to work on this, but I dislike the idea of having to maintain a duplicated flatpak extension for each browser. Edit: How could I miss #49 |
KeePassXC-Browser extension can't connect to native KeePassXC instance.
(It says:
Key exchange did not succeed.
).I don't know if I should report it here or on KeePassXC-Browser repo, but it works with native Chromium browser provided by Debian so I guess it's not it's fault.
Here is an extenstion activity log: exported_activity_log_oboonakemofpalcgghocfoadofidjkkk.txt
Also the Chromium output:
My OS:
The text was updated successfully, but these errors were encountered: