Opening Master palette with Shift+F9 causes Musescore to crash

• Jun 20, 2018 - 16:17
Reported version
2.2
Type
Graphical (UI)
Severity
S3 - Major
Status
closed
Project

Hey Everyone!
One day, I was working on my scores, just the usual jazz, and then Musescore (for some reason) crashed as I was opening the "Masterpalette" (Shift + F9). Then, after I restarted the program, I tried to open the "Masterpalette"; and it crashed again. And every other time afterwords. So, basicly saying, I can't make any "non-basic" time signitures, because it just keeps crashing. Can you fix this problem please? It's super annoying.
Thanks! :)


Comments

Title Masterpalette = Musescore crash Opening Master palette with Shift+F9 causes Musescore to crash

Have you tried opening it using either shift+t to open directly to time signatures or by pressing z which also opens the master palette. I never use shift+F9 and I've never experienced this crash. The crash does need to be fixed, but this might help you get where you need to be.

Another thing to look at is to see if you have defined shift+F9 for something else, most likely a plugin. MuseScore does not look for this as a conflict. Also make sure "Show Master Palette" has Shift+F9 assigned as its shortcut.

Shift+F9 works fine on my computer.

Same/similar here (Windows 10 and 7, MuseScore 2.2.1). Opening the master palette doesn't crash here, not via Shift+F9 and not via View→Master palette. So somethign got to be different between my and your setup. Maybe it is as simple as upgrading to 2.2.1 (I don't see anything promising in the 2.2.1 release notes though, except maybe the crash reported in #270748: [Regression] Playback slow to engage, when starting playback too quickly after load score)? Or revert to factory settings?

In reply to by mike320

{Reply to mike320} Hey! Just now, I've tried all of the possable shortcuts you suggested, and intertrestingly, the program crashes to all of them. I've also checked if the shortcut matches the master palette, and it does. So I changed it to another combination, to see if it made any difference, and even with that, the outcame was the same.
I feel like I've done almost everything to fix this problem. I've even reinstalled Musescore two times, along with trying out a 'Repair Musescore' funcion upon installing, but it really seems that my problem is personallised, not general.