Santiago González

Not really. You just have to be really fast

@pail459 I'm using Sumatra PDF. I'm not editing anything. @dreichl video should be better. Sumatra PDF is opening in another monitor, so I just recorded what I did with KeePass to reproduce the error message. It's harder to reproduce the file name error message though.

[FR] Error when discarding changes after quickly opening an attachment

[FR] Per-sequence Two-Channel Auto-Type Obfuscation

English is not my first language, so I may not have explained the issue clearly before. I have now attached screenshots to illustrate it better. "Google (t...)" is the original entry, which was last modified on 2026-05-26. "Google (a...)" is the duplicated entry. In KeePass history, it appears as if it was modified on 2026-05-26, but that timestamp is incorrect, since I duplicated the entry only a few days ago. If you look at the duplicated entry's own history, you can see that I actually created...

This is particularly problematic when reviewing the global history. Recently duplicated entries may not appear among the newest entries because they inherit an old creation timestamp from the original entry. If the original entry was created or last modified months or even years ago, the duplicated entry can appear far back in the history even though it was actually created recently. As a result, the global history becomes unreliable for identifying entries that were created recently.

Duplicated entry inherits an incorrect creation time

Tysm! I tested it with all the XML replacements I wanted to apply, including renaming custom fields and modifying their values, and I couldn't reproduce the bug. It's working flawlessly now!