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

MacOS: two instances opening after pressing hotkey #1216

klara31 opened this Issue Nov 23, 2017 · 7 comments


None yet
8 participants

klara31 commented Nov 23, 2017

I am using KeepassXC on MacOS. When I press the hotkey to autotype a password in Safari, two instances of KeepassXC are opening to enter the database password.
schermafbeelding 2017-11-23 om 08 52 10

If I enter the password in one of the instances (in this case: the one on top), the following error is displayed:
schermafbeelding 2017-11-23 om 08 55 30
(translated: could not find an element with window title: About KeepassXC)

Expected Behavior

Only one instance should open.

Current Behavior

Two instances open

Steps to Reproduce (for bugs)

Press hotkey combination to autotype username and password in Safari

Debug Info

KeePassXC - Version 2.2.2
Revision: 6d46717


  • Qt 5.9.1
  • libgcrypt 1.8.1

Operating system: macOS High Sierra (10.13)
CPU architecture: x86_64
Kernel: darwin 17.2.0

Enabled extensions:

  • KeePassHTTP
  • Auto-Type
  • YubiKey

@weslly weslly self-assigned this Nov 26, 2017


This comment has been minimized.

RicardoCapricciosa commented Dec 6, 2017

I can confirm this issue, but it occurs only if the database is locked.


This comment has been minimized.

hfr-hfr commented Mar 1, 2018

This is still an issue with v2.3.0

@TheZ3ro TheZ3ro added this to the 2.3.1 milestone Mar 1, 2018


This comment has been minimized.

anshulbajpai commented Mar 1, 2018

Yes, this issue still exist


This comment has been minimized.

anshulbajpai commented Mar 1, 2018

I'd like to add more to this bug.
When we press the global hotkey to summon auto-type (with the browser in foreground) on a closed database and after entering the password, we see a modal dialog saying "Couldn't find the entry that matches the window title: **** - KeePassXC".
When we press the OK button, then the KeePassXC application is in the foreground, whereas the expected behaviour would be to bring the browser again in the foreground.


This comment has been minimized.

emilbayes commented Apr 1, 2018

The problem with focus seems solved for me in 2.3.1, but it still cannot find the correct password if the database was previously locked


This comment has been minimized.

hfr-hfr commented Apr 3, 2018

Yes, the issue still exists in 2.3.1-2.3.3:

Focus is now set correctly on password field. But the other issue (using wrong window title for autotype) remains. Here's my summary of this bug from October last year:

after unlocking the database (…) KeepassXC should use the prior window (where global Auto-Type keyboard shortcut was invoked) to check against auto-type rules. Instead it uses its own window ("database-name KeepassXC") and consequently presents an error dialog "no entry found with that window title".


This comment has been minimized.

klara31 commented May 14, 2018

Problem still exists in 2.3.3

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