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

Try other (still locked) database on auto-type not found #4777

Closed
wilriker opened this issue May 25, 2020 · 1 comment
Closed

Try other (still locked) database on auto-type not found #4777

wilriker opened this issue May 25, 2020 · 1 comment

Comments

@wilriker
Copy link

Summary

It would be helpful to either
a) be able to select the database to be unlocked by first auto-type invocation or
b) if no entry was found in the just unlocked databases and other locked databases remain to let the user unlock them as well.

Context

I usually have two databases in my KeepassXC instance. After start-up both are locked and when I first use auto-type it will ask me to unlock one of them (I have not yet found a pattern which one that is). Most of the times of course this is the wrong one and it will not find the required entry (I unlock it anyway since I usually need both databases sooner or later).

@droidmonkey
Copy link
Member

Duplicate of #2322

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

No branches or pull requests

2 participants