Crash entering note input mode on percussion staff after changing panel preference

[MarcSabatella]

Issue type

Crash or freeze

Description with steps to reproduce

The following crash is reproducible if you start out with your percussion panel set to display "When an unpitched percussion staff is selected" and to "Close the panel automatically". From that point:

1. create a new score with a percussion staff
2. click an empty measure on the percussion staff to select it (note: the Percussion panel opens)
3. open Preferences / Percussion and change to display the panel "When inputting notation on an unptiched percussion staff"
4. click OK to close Preferences (note: the Percussion panel remains open)
5. enter note input mode

Result: crash

I'm assuming this has to do with the fact that it is not expecting the panel to be already open, now that I've changed the preference. And it doesn't always crash if I've previously opened and closed the panel or fiddled with Preferences a bunch prior to doing this. But for me at least, it always crashes if I follow these steps exactly.

Supporting files, videos and screenshots

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250590404, revision: github-musescore-musescore-b05197f

Regression

No.

Operating system

Debian 12

Additional context

(we could really use an option under regression to say "N/A - functionality did not exist in previous releases")

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[zacjansheski]

I didn't reproduce this on MacOS. Please share diagnostic files.

"Regression status" is only useful to trace the cause of the problem, so new feature issues are just not regressions, no need for an additional option, the team will triage accordingly.