Database corrupted a second time: Could it be KeePassium?

[lajawi]

In a matter of 8 days, my KeePass database has corrupted a second time.

The first time, I had issues with an Invalid inner header id size (which I asked about on keepassxreboot/keepassxc), but this time around, I get No root group as an error in KeePassXC on desktop.

Both times, the issues first arose in KeePassium, making me suspicious of what KeePassium is doing with my database.

Right before the first corruption, I enabled a new feature with autofill that tries to save the entry used for a specific site, maybe that is causing issues?

In both cases, KeePassium also told me I have unsaved changes, but since I can't open the database, these can't apply either.

Setup

My setup is currently as follows: on my desktop I use KeePassXC to manage my database, I sync it with the Nextcloud Client app to a private server. On KeePassium, I added the database via WebDav.

Maybe this could help identify possible issues.

[keepassium]

This might be KeePassium, yes: saving changes in/after AutoFill is a new feature and while beta tests went well, things might misfire in edge cases in a wider audience.

In both cases, KeePassium also told me I have unsaved changes, but since I can't open the database, these can't apply either.

The unsaved changes can still be applied, but let's figure out how much preparation is needed.

• When you get "No root group": is the file substantially smaller than its earlier/good version?
• How long does saving your DB typically take? Less than a second? A couple of seconds? Longer? There is a known issue in v2.4 that can cause DB corruption in longer saves.

[keepassium]

I will need to test whether we can do something about it.

Ok, so interrupted WebDAV transfer should not be an issue. When uploading, KeePassium sends data along with the Content-Length header. According to the specs, when the server receives fewer bytes than promised, it should reject the request (and consequently not overwrite the file with an incomplete one).

So this must be either the overlapping saves or something yet unknown.

[lajawi]

As an immediate fix, you would need a few preparation steps...

Since my latest backup was from my PC (and I haven't changed anything in the database that's of importance on my phone for a while), I got that one and overwrote the file in NextCloud from my desktop, before doing so I removed the connection on KeePassium just to be sure.

QUICK EDIT: After reconnecting the database via NextCloud WebDav, it still had "unsaved changes", they now synced and all seems to be working again. I didn't know KeePassium could remember changes even if the database got fully disconnected.

[lajawi]

So this must be either the overlapping saves or something yet unknown.

I opened this discussion to gain some insights and see whether or not it was just me doing something wrong or a real issue.

Should I open an issue on the matter?

[keepassium]

The freemium v2.5 is already in the App Store (Pro will follow in a day or so).
Give it a try and if the issue remains — create an issue. Thanks!

[lajawi]

The issue remains, so I opened #482