When I shutdown computer (Arch Linux, Mate) without exiting KeePassXC manually, the .db-name.lock file remains in the folder and blocks KeePassXC from opening the db file next login (it is automatically started on logon). Even when confirming "yes, open the file anyway", the original lock file remains in the folder and the user has to delete it manually (in terminal, since it is a "hidden" file, which are usually not displayed in the file managers by default).

Expected Behavior

KeePassXC should avoid using lock file on db.

Current Behavior

On force close, the lock file remains stale. It does not get deleted even on forced re-opening by user.

Possible Solution

Instead, it should read the db before save and merge any changes. (The same way as Keepass2Android does it.) It would also resolve a problem of file syncing in the background (e.g. via Dropbox) with other clients/systems.

Your Environment

• KeePassXC version/commit used: 2.0.3
• Operating System and version: Archlinux.