Bogus and useless corruption message

[Jojo-Schmitz]

Issue type

UI bug (incorrect info or interface appearance)

Bug description

No response

Steps to reproduce

Open the score from https://musescore.org/en/node/358354
(or the one attached here Alimento Espiritual.zip)

Error message:

No filename, no error detail.
From the log.

2023-12-27T16:53:02.455 | ERROR | main_thread | Read410::readScore410 | MSCX Fehler in Zeile 0: Ungültige Taktlänge: 1728/768
2023-12-27T16:53:02.456 | ERROR | main_thread | NotationProject::load | failed load, err: [2010] Die Datei „“ ist kritisch beschädigt und kann nicht bearbeitet werden.

Proper details, except for the wrong line number and, again, the missung filename.

Mu3 (rightfully!) reports (on the mscx, resp. Mu3.7 on the mscz):

Filename, line number and the error itself

How the score got into that corrupt state is a different issue... the score stems from Mu 4.1.1

Screenshots/Screen recordings

No response

MuseScore Version

4.2.0

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 11

Additional context

No response

[bkunda]

@cbjeukendrup could you please investigate this?
I recall the reason for this dialog variant was that MS4 couldn't actually open the file at all (as opp. to the "open at your own risk" variant).

[Jojo-Schmitz]

Whether Mu4 can open the file or not is not really relevant here, this issue is about the error message being wrong, incomplete and useless

[Jojo-Schmitz]

In https://musescore.org/es/node/358525 you'd find another score corrupted in this way

[Jojo-Schmitz]

Another occurrence in https://musescore.org/en/node/358820

[Jojo-Schmitz]

And another, https://musescore.org/en/node/360049

We'd still need another issue for those bogus measure durations, but I have no idea how to reproduce this

[Jojo-Schmitz]

Came up in https://musescore.org/en/node/364069 again