hello everyone,

I use the newest KeePass version and use the option "Lock workspace after KeePass inactivity (sec):". This works fine, but if I open an entry in KeePass and exceed the lock time then nothing happens, no lock is active!

I hope someone can help me, thanks!

I may have duplicated this problem. Here's what I did:

I turned on the locking feature. After 30 seconds, the database locked.

I unlocked it and modified it by adding a test entry. 30 seconds, the KeepassX displayed a message asking whether I wanted to save the modification. I clicked "No" and the database locked, deleting the test entry.

I unlocked the database, created another test entry, and then used "Save As" to save the modified database. After 30 seconds, the new database locked.

However, when I opened a dialog for editing an existing entry, the database did not lock while they dialog was open. Once I closed the dialog, the database locked in 30 seconds. Is this the specific behavior you are concerned with.

Given that locking a database with unsaved changes discards those changes, I would not consider not locking a database that is actively being edited to be a bug.

hello frankbell! Thanks for duplicating the problem! Yes this is my problem:

"However, when I opened a dialog for editing an existing entry, the database did not lock while they dialog was open. Once I closed the dialog, the database locked in 30 seconds. Is this the specific behavior you are concerned with."

..and I understand that locking the database maybe ends in information lost, but if one opens the dialog only for copy user/pass or some other information without to edit something then I think the database can be locked.

You should not have to open the editing dialog to copy a username, URL, or password. You need only point to the entry in question and right-click; KeepassX will present a dialog including "Copy Username to Clipboard," "Copy Password to Clipboard," "Copy URL to Clipboard," as well as some other choices.