Opening Page settings crashes app

• Jun 16, 2021 - 09:27
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
Yes
Project
MuseScore

Steps to reproduce:
1) open attached file
2) click Format > page settings

Observed behavior:
what would be the page settings menu is black and app unresponsive

Version:
OS: Ubuntu 20.04.2 LTS, Arch.: x86_64, MuseScore version (64-bit): 3.6.2.938029273, revision: 415b192

Attachment Size
Pelirrojo_crash.mscz 16.11 KB

Comments

• Jun 16, 2021 - 09:59

Whether it's a duplicate depends a lot on the inner cause of the crash.
I have so far not found a workaround other than starting from scratch. Deleting the part does not fix it for me.

On that note: I would call deleting a whole voice not really a valid workaround. The original file is a lot bigger and I really don't want to have to recreate the whole voice.

Reply

• Jun 16, 2021 - 11:29

Is it a post 3.6.2 regression, does it happen with the official 3.6.2 AppImmage too, or just with your latest 3.x self-built version? Which Qt version is used?

Reply

• Jun 16, 2021 - 11:36

" as such seems to be corrupt in some way."
Indeed, by deleting the last measure in Alto part, the corruption appears clearly - images below.
Related I guess (?) to the nested tuplets (@ct2034: what exactly was your aim with these nested tuplets - unexpected nested tuplets (?) - , were you sure you wanted to get these tuplets this way?)
Anyway, as said previously, deleting this part and recreating it solves the problem since, after that, this measure is identical (with only one eighth note on the first beat) in the main score and the part.

nestuplet.jpg
nestuplet1.jpg

Reply

• Jun 16, 2021 - 13:01

Okay, to clarfiy:
1) @cadiz1 This issue (page settings opening) can NOT be solved by deleting and adding the part. At least not for me. After removing and adding the parts, I can still not open the page settings. I therefore don't think it's a duplicate. At least, there is no workaround for this problem. And it is highly annoying for me.
2) @Jojo-Schmitz It is also existing in 3.6.2 release version.
3) @cadiz1 I obviously never setup up the tuplets in this way. Maybe this is the core problem. (But the file was originally probably created by an older version. I honestly don't remember)

Reply

• Jun 16, 2021 - 13:16

With -d, i get nothing while waiting, but when the settings show up, I get

qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205
qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205
qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205
qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205
qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205
qt.svg: /usr/share/icons/Faba/16x16/actions/dialog-ok.svg:112: Could not resolve property: linearGradient4205

Don't know if this helps

Reply

• Jun 16, 2021 - 13:19

"This issue (page settings opening) can NOT be solved by deleting and adding the part. At least not for me. After removing and adding the parts, I can still not open the page settings."
Well, here, after deleting/recreating part (Windows 10, version 3.6.2), opening Page settings works just fine, and immediatly

"I obviously never setup up the tuplets in this way. Maybe this is the score problem. (But the file was originally probably created by an older version."

Score problem? Surely. Created by an older version? Maybe/likely.

EDIT: By the way, here again, the Page Settings opens normally with the corrupted part.
page.jpg

Reply