Not well-formed (invalid token) error when importing a Linux backup file on Windows 11

While trying Gramps 5.1.5 on Windows 11, I found this error during import of a large backup file, created with Gramps 3.4.9 on LMDE 2:

not well-formed (invalid token): line 5767187, column 17

I have not inspected the Gramps XML yet, but I’m wondering whether anyone else has seen an error like this.

On closer inspection, 7-Zip and gunzip found a CRC error in the compressed backup, which was probably caused by a faulty thumb drive. Gramps did not mention that however.

1 Like

Which brings me to a follow-up question. Shouldn’t Gramps show that CRC error instead of failing on a malformed piece of XML? I ask that, because a small corruption can slip through when it doesn’t mess up the XML.