Expected Behavior

The database lockfile should be removed when the database auto-locks, if a timeout is configured.

Current Behavior

The database auto-locks, but the lockfile remains.

Possible Solution

Delete the lockfile when the database is auto-locked, the same way it's deleted when the database is closed.

Steps to Reproduce (for bugs)

1. Configure an auto-lock timeout
2. Open a database
3. Wait for the timeout to trigger auto-locking
4. Verify if the lockfile exists

Context

When a database is accessed by multiple users on a network drive, a frequent problem encountered is users forgetting to close KeePassXC, thus preventing other users from modifying it. This problem could be avoided if all users had an auto-lock timeout configured, and if auto-locking would remove the lockfile, allowing other users to modify the database when it's unused. If a user unlocks a database after being auto-locked, the lockfile would be re-created, unless a new lockfile already exists, in which case the database would be simply re-opened in read-only mode.

Your Environment

KeePassXC 2.2.1 in Windows