Auto-Type with database locked uses KeePassXC window title

[robdevops]

Expected Behavior

After prompting to unlock the database, KeePassXC should search for an entry matching the window which was focused when the global auto-type shortcut was triggered.

Current Behavior

KeePassXC opens a dialog: "Couldn't find an entry that matches the window title " - KeePassXC".

Steps to Reproduce (for bugs)

1. Lock Database
2. Focus another app
3. Press Global Auto-Type Shortcut
4. Enter unlock password and hit Enter.
   (Dialog appears now)

Debug Info

KeePassXC - 2.3.4

Libraries:

• LIBS

Operating system: macOS 10.13.6
CPU architecture: x86
Kernel: Darwin Kernel Version 17.7.0

Enabled extensions:

• defaults

[TheZ3ro]

Can someone test this on macOS? I cannot reproduce this on Linux

[ChristopherSchultz]

This happens to be 100% of the time. Basically, auto-type + locked database = no workee.

Also see #1982, #1216, #947 which I believe are all reports of the same problem under different descriptions.

[robdevops]

This issue differs from #1982 as described, because it works perfectly with the database unlocked.

It appears directly related to #1216, and redesigning that is likely to fix this.

#947 was logged for an older version of KeePassXC which did not support prompting to unlock the database when the global autotype hotkey was pressed, although there is discussion of this issue in newer versions of KeePassXC in the comments of that Issue.

[ChristopherSchultz]

@solikeumyeah I was just trying to tie-together a bunch of related issue reports, since they all seemed to be different sides to the same coin. Your report seems to be the best-described of all of them, because the other reports seem to guess that there is a much more specific problem, when the core issue is quite generic.

[robdevops]

Dying for a fix. Is there any further info or clarification I can provide for this bug?

[droidmonkey]

I can replicate it, looks like what is happening is that when the modal unlock dialog appears it raises the KeePassXC main window as well. This is likely a specific Mac behavior because that does not happen on Windows or Linux. The modal unlock window should not be used on Mac and I agree that Autotype should not "remember" KeePassXC window as the last window used.

[robdevops]

Here is a video of the behavior for those who don't have a Mac.
https://youtu.be/NKp0DPju14k

Sequence of events:

1. I press [global auto-type hotkey] when prompted for my sudo password.
2. I unlock the database and dismiss the KeePassXC error.
3. I press [enter] in the terminal to demonstrate my password was not auto-typed.
4. I press [global auto-type hotkey] in the terminal a second time to demonstrate it works with the database unlocked.

[droidmonkey]

This is a duplicate of #1216

[Joachim-42he]

I am seeing the same behaviour.

Debug Info
KeePassXC - Version 2.4.1
Revision: 7bafe65

Qt 5.12.2
Debugging mode is disabled.

Operating system: macOS Mojave (10.14)
CPU architecture: x86_64
Kernel: darwin 18.6.0

Enabled extensions:

• Auto-Type
• Browser-Integration
• SSH-Agent
• KeeShare (only unsigned sharing)
• YubiKey
• TouchID

Cryptographic libraries:
libgcrypt 1.8.4