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

"KeepassXC-Browser has not been configured" even though it has #316

Closed
Mrfiregem opened this issue Oct 17, 2018 · 4 comments
Closed

"KeepassXC-Browser has not been configured" even though it has #316

Mrfiregem opened this issue Oct 17, 2018 · 4 comments

Comments

@Mrfiregem
Copy link

Expected Behavior

After connecting the extension and KeepassXC program by naming and accepting the association request key, the extension will remember that it's been connected the next time Firefox restarts.

Current Behavior

After restarting the browser, KeepassXC-Browser asks again to connect to KeepassXC. When looking in the extension's settings page, the key is already listed under connected databases.

Steps to Reproduce (for bugs)

  1. Enable Firefox browser integration in KeepassXC
  2. Install KeepassXC-Browser from the AMO
  3. Click Connect, name and accept key
  4. Expect extension to remember that it's been configured after restarting Firefox

Debug info

KeePassXC - 2.3.1
KeePassXC-Browser - 1.3.0
Operating system: Xubuntu 18.04.1 LTS x86_64
Browser: Firefox 62.0.3 (64-bit) [From apt repo]

@varjolintu
Copy link
Member

Update the KeePassXC. Use the official PPA or AppImage.

https://launchpad.net/~phoerious/+archive/ubuntu/keepassxc

@Mrfiregem
Copy link
Author

Solved. Using ppa rather than outdated repo fixed it.

@jsachs
Copy link
Contributor

jsachs commented Oct 17, 2018

@varjolintu can you briefly explain why this happens? We maintain a fork of KeePassXC and are seeing this issue, and would like to correct it ourselves.

@varjolintu
Copy link
Member

@jsachs It's been a long time since 2.3.1, so I really don't have a valid anwser for that. Wouldn't it be easier to update your fork?

Looking at the history since 2.3.1, it might be related to this:
keepassxreboot/keepassxc#1720

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