HELP PALETTE DISAPPEARED! I'm desperate!

• Jun 27, 2013 - 01:01

My palette disappeared and there's nothing I can do to get it back. I even re-loaded the program. If I ask it to display the palette, it shows me a blank box. HELP!!!!!!

Comments

xavierjazz

• Jun 27, 2013 - 01:07

Press F9. Does that help?

NewMusicScoreUSerGerald

• Jun 27, 2013 - 02:29

No, pressing F9 doesn't bring up the Palette menu -- it brings up an empty icon for it. Clicking on the icon doesn't do anything.

schepers

• Jun 27, 2013 - 04:00

Sound like you need to reset to factory: http://musescore.org/en/handbook/revert-factory-settings

NewMusicScoreUSerGerald

• Jun 27, 2013 - 17:56

Thanks Schepers, resetting did the trick. I could never have figured out how to do the reset without your help. Thanks a million!

jsaini

• Jun 14, 2019 - 00:29

On a mac, if you click on the musescore window and at the top, if you go to 'view' then you click on 'palettes' then the palette should come back, it worked for me

Attachment	Size
Screen Shot 2019-06-14 at 9.28.38 am.png	299.19 KB

jckemp07

• Aug 5, 2020 - 03:00

This helped, Thanks!

Tiaan Smit

• Jun 9, 2023 - 15:17

Thank you kind sir

Jojo-Schmitz

• Jun 27, 2013 - 08:46

Does http://musescore.org/en/node/20767 help?

Michael Hillside

• May 14, 2016 - 09:02

I had the same problem and I found this discussion, Thank you for advice.

Pansmanser

• Sep 28, 2019 - 11:24

Using musescore 3 appimage on Ubuntu 16.04, my palettes have likewise disappeared. The left panel displays 'palettes' with a blank space. Reset does not remedy. Help, please!

Attachment	Size
screen.png	71.82 KB

Jojo-Schmitz

• Sep 28, 2019 - 11:33

That is a 3.3 Beta and as such not related to anything previously mentioned in this thread. Which version exactly (Help > About)? What version of Qt is installed on your machine?

Pansmanser

• Sep 28, 2019 - 15:00

musescore 3.3.0. Qt 5.9.3
But it was working with this version when first installed.
Perhaps not directly connected, but it seems a very similar problem.

Jojo-Schmitz

• Sep 28, 2019 - 16:22

The entire palette is new with 3.3, usung an entirely different approach thatn before.
Still a factory reset should do the trick of bringing it back.

Pansmanser

• Sep 28, 2019 - 17:42

But unfortunately it did not. I have reverted to 3.2.3, which has fixed the problem. Thanks for help, anyway.

Marc Sabatella

• Sep 28, 2019 - 18:35

The screenshot looks like the first beta, did you try the second (current) beta?

Pansmanser

• Sep 28, 2019 - 20:20

I was running 3.3.0 (that was the screenshot) and have reverted to 3.2.3. Previously (a month or so ago) it was v2.

Marc Sabatella

• Sep 28, 2019 - 20:27

Yes, but I'm pretty sure it was the first beta of 3.3.0 in your screenshot. I think the second (current) beta would probably work for you.

Pansmanser

• Sep 28, 2019 - 20:33

Thanks for this. I'll give it a try, but it will be into the coming week now.

kuwitt

• Sep 28, 2019 - 20:30

Indeed, check Beta 2 of MS 3.3.0 (https://musescore.org/en/3.3beta2).
Maybe also check, if there's any difference by switching the workspace.

For me the palette view of the AppImage works with OpenSuse Leap and XFCE.

Pansmanser

• Sep 29, 2019 - 21:32

Mysteriouser and mysteriouser! The attachment is the starting screen with beta 2.

Attachment	Size
screen2.png	54.13 KB

Jojo-Schmitz

• Sep 29, 2019 - 22:07

Certainly not the factory settings

Marc Sabatella

• Sep 29, 2019 - 23:24

Right, so definitely do a Help / Revert to Factory Settings.

Pansmanser

• Sep 30, 2019 - 10:08

This screen image is from the beta2 , run from terminal with -F. Is there anything else I can do to get a more 'virgin' version? I have v3.2.3 on the system, and I notice that the settings on v3.2.3 have also been disrupted by the reset, which is to be expected. But I don't know if there is some other setting 'left over' from that installation. Also it was not the first time I had run beta2.

Attachment	Size
screen3.png	56.67 KB

Jojo-Schmitz

• Sep 30, 2019 - 10:10

Well possible that there are components missing for/from AppImages and 3.3's new palettes.

My bet is on libQt5Quick{Controls,Templates}2.so.5 or some files from the qml directory

kuwitt

• Sep 30, 2019 - 14:49

As mentioned by using the AppImage of 3.3.0 beta the palette view looks fine for me with OpenSuse Leap and wm XFCE (as both: for beta1 and beta2 - see attached file).

Would be interesting, if an other user (with Ubuntu/Ubuntu derivate/other Linux system) can reproduce it and figure out what could be the reason, that there are no problems with 3.2.3, but with 3.3.0 beta for the user.

Attachment	Size
palettes.png	103.8 KB

Pansmanser

• Sep 30, 2019 - 15:36

OK, we'll wait and see. I think it's because of something I accidentally altered, because originally the first beta was working normally. Meantime I'm happy using 3.2.3.

mtuliosax

• Oct 2, 2019 - 15:09

I am in the same trouble. All palettes are blank. In fact, all elements are there (cells). They are selectionable but invisible. I have already downloaded another appimage and even reset to factory settings.

kuwitt

• Oct 2, 2019 - 15:19

Which Linux distribution (with version number)? And 3.2.3 works for you too? It seems that's isn't in general, but some distributions have trouble with the actual beta...(?).

mtuliosax

• Oct 2, 2019 - 15:35

3.2.3 works perfectly. My OS is Xubuntu 18.04. At first both 3.3 beta and update worked perfectly. Suddenly the problem occurred. I also tried some nightly builds and the bug persists.

Pansmanser

• Oct 2, 2019 - 17:14

(I see I said Ubuntu 16.04, but in my case it should also be 18.04)

dmitrio95

• Oct 3, 2019 - 08:34

Could you please attach a screenshot of your palettes? Do those cells have correct tooltips, and are you able to apply them to a score with dragging or double-clicking?

mtuliosax

• Oct 3, 2019 - 11:28

Voilà! Yes, I can apply the cells both by dragging or double-clicking. Thank you!

Attachment	Size
MuseScore 3.3 Relese Candidate Portable AppImage: Sem título-_070.png	2.91 MB

Jojo-Schmitz

• Oct 3, 2019 - 11:32

So the palette cells are not empty, 'just' invisible or white on white it seems?

mtuliosax

• Oct 3, 2019 - 11:37

Yes. I can reach them.

Jojo-Schmitz

• Oct 3, 2019 - 11:42

tooltips (when hovering over those palette cells) don't show either?

mtuliosax

• Oct 3, 2019 - 14:19

Tooltips are visible.

Jojo-Schmitz

• Oct 3, 2019 - 14:35

Seems same or similar issue just came up in https://musescore.org/en/node/295218

dmitrio95

• Oct 4, 2019 - 11:59

Very interesting, even button text is not visible... If running AppImage from a command line, does it show any output? Could perhaps the problem disappear after closing/reopening palettes (F9) or resizing that left panel perhaps?

kuwitt

• Oct 4, 2019 - 18:42

Cames up again in German forum (there with Linux mint): https://musescore.org/de/node/295249

dmitrio95

• Oct 4, 2019 - 19:58

That case looks different though, there palettes do not appear at all, and in this thread it seems to be reported that palettes are shown but no text or cell icons visible on them.

Pansmanser

• Oct 4, 2019 - 20:04

In my case, reported above, palettes did not appear at all with Beta 1.

dmitrio95

• Oct 4, 2019 - 20:12

Then I would like to ask you to try running the AppImage from a command line as well and post an output here if there is any, that could help to diagnose the problem.

Pentatonus

• Oct 4, 2019 - 22:31

Here is my output from console:

Attachment	Size
ConsoleOutput.png	31.96 KB

Pentatonus

• Oct 4, 2019 - 22:21

Hello, i am the guy from the german forum. Addition: i can click on the invisible palettes. Tooltips show up and the functions apply to the score.
Greetings, Pentatonus

Attachment	Size
PalettesInvisible.png	233.79 KB

AndreasKågedal

• Oct 5, 2019 - 16:41

I have a very similar problem. The palette is completely blank (and before that, the start-center is also empty with a black canvas), right-clicking in the paletet brings up some alternatives. and When I close MuseScore I get some more output in the terminal:

andka@jojoba:~$ Downloads/MuseScore-3.3.0-Beta2-x86_64.AppImage 
Jack appears to be installed on this system, so we'll use it.
QApplication: invalid style override passed, ignoring it.
QMutex: destroying locked mutex
qrc:/qml/palettes/Palette.qml:347:25: Unable to assign [undefined] to bool
qrc:/qml/palettes/Palette.qml:347:25: Unable to assign [undefined] to bool
/... Lots of these .../ 
qrc:/qml/palettes/Palette.qml:347:25: Unable to assign [undefined] to bool
qrc:/qml/palettes/Palette.qml:347:25: Unable to assign [undefined] to bool
QObject::disconnect: No such slot Ms::MyWebView::stopBusy(bool)

In Ubuntu 18.04 and using the Appimage for 3.3, Beta 2

dmitrio95

• Oct 7, 2019 - 12:11

Did you try the latest Release Candidate version? The issue seems to be reported for that version too though.

mtuliosax

• Oct 7, 2019 - 12:22

I've tried RC. The problem persists. I attach my output on terminal.

Attachment	Size
3.3 release candidate output.txt	2.8 KB

dmitrio95

• Oct 7, 2019 - 13:30

Could you please also try something like

QT_LOGGING_RULES="*.debug=true" ./MuseScore-3.3.0-RC-x86_64.AppImage &> musescore_output.txt

and attach that musescore_output.txt here? That should give somewhat more verbose output.

mtuliosax

• Oct 7, 2019 - 14:17

Of course!
Voilà!

Attachment	Size
musescore_output.txt	4.76 KB

dmitrio95

• Oct 7, 2019 - 14:54

Did MuseScore fully launch when you recorded this file? And did you close MuseScore before sending the file? For me the same command yields more output in that file, it would be interesting to see that part too.

mtuliosax

• Oct 7, 2019 - 21:00

Sending again. I think it is ok now.

Attachment	Size
musescore_output.txt	1.83 MB

kuwitt

• Oct 7, 2019 - 17:20

As mentioned, until now I can't reproduce it with Opensuse Leap by using XFCE (checked with Beta 1, Beta 2 and RC), so it doesn't seem to be an issue in general for me and don't have a clue of it.
Some thoughts: AFAIK an AppImage should have includes all necessary libraries. Still I wonder, if it could be a "unity" issue (but shouldn't be) and if there's any difference, if one of the Ubuntu/Mint users would run the application with another window manager.
(I didn't check the AppImage with the Qt variable before inside the terminal as mentioned)

dmitrio95

• Oct 7, 2019 - 22:59

I tried running MuseScore in Ubuntu 18.04 inside Virtualbox and asked two people with Ubuntu 18.04 and Mint on their computers to try running 3.3 RC too. In all those cases palettes work properly. So it doesn't even seem to always be the case in Ubuntu.

Jorge Eduardo Jonas

• Oct 8, 2019 - 06:59

I'm on Ubuntu Studio 18.04, the palettes worked properly on Beta version, and after a few days I had the text disappearing issue, and currently persist on RC, maybe due to some system actualization?

dmitrio95

• Oct 8, 2019 - 09:41

> maybe due to some system actualization
Did you install some system updates before the issue happened? Or which actualization do you mean here?

I am not sure this is going to help, but perhaps you could try removing QML cache for MuseScore:

rm ~/.cache/MuseScore/MuseScore3/qmlcache/*

Jorge Eduardo Jonas

• Oct 8, 2019 - 12:46

It was probably after a sudo apt update, the cache removal did not work unfortunately.

mtuliosax

• Oct 8, 2019 - 16:20

For me too. Removing cache was useless.

Jorge Eduardo Jonas

• Oct 9, 2019 - 08:33

Weirdest thing happened, I updated Skype for linux, and the text is now visible in the palette...

jeetee

• Oct 9, 2019 - 08:54

I know that (at least back around v4) Skype used to use Qt for its GUI on linux; but afaik it now runs on GTK+.
Perhaps you still had an older version, forcing a Qt version conflict with MuseScore before?

Jorge Eduardo Jonas

• Oct 11, 2019 - 07:29

hmm I had a version 8. something so it was quite recent ...

mtuliosax

• Oct 9, 2019 - 14:32

Good for you. I've tried the same but no results.

mtuliosax

• Oct 9, 2019 - 14:49

One question: 3.2.3 uses Qt version 5.12.5. (following Help menu) but 3.3 (both beta and RC) uses Qt version 5.9.3. Could not this be related with the issue?

Jojo-Schmitz

• Oct 9, 2019 - 15:42

On what OS? on Windows 3.2.3 uses Qt 5.12.2 and 3.3RC uses 5.12.5, on macOS either uses Qt 5.9
On Linux it uses whatever is installed there, not sure which version the AppImages use though.

kuwitt

• Oct 9, 2019 - 15:52

The AppImage of MS 3.3RC is using 5.9.3 (although it would be nice to change it to 5.12.x, if possible - for example to use "dead keys").
Not sure if there could be a conflict between the QT-version inside the AppImage and the installed QT-version of the OS.

mtuliosax

• Oct 9, 2019 - 15:53

XFCE
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"

Attachment	Size
QT version.png	83.71 KB
musescore version.png	31.95 KB

Jojo-Schmitz

• Oct 9, 2019 - 15:56

It indeed should use 5.12.5, I see no neend for it to stick with 5.9 (unlike the macOS version)

kuwitt

• Oct 9, 2019 - 16:07

IIRC there was a commit some months ago of Anatoly-os to change it, but was changed back, maybe it didn't work properly.

Jojo-Schmitz

• Oct 9, 2019 - 16:47

Hmm, yes, it might have had a bad impact at some other place

dmitrio95

• Oct 9, 2019 - 22:21

> One question: 3.2.3 uses Qt version 5.12.5. (following Help menu)

For me AppImage for 3.2.3 and all the other 3.X versions show that they use Qt 5.9.3. We tried switching to 5.12.5 but ended up with not changing Qt version for AppImage due to concerns on compatibility with different GNU/Linux distributions. So all release AppImage builds of MuseScore located on musescore.org should actually use Qt 5.9.3. Did you get 3.2.3 version in some other way (by downloading some nightly build perhaps), or do you have Qt 5.12.5 installed somewhere in your system?

mtuliosax

• Oct 9, 2019 - 22:48

I've installed by ppa. https://launchpad.net/~mscore-ubuntu/+archive/ubuntu/mscore3-stable
I choose that mainly because I am Brazilian. So I speak portuguese and I need special characters and appimage does not permit dead keys (Now I know it is because Qt version).

Jojo-Schmitz

• Oct 10, 2019 - 07:53

Ah, that's a pity. That way we'd never get rid of that deadkey bug in AppImages

kuwitt

• Oct 10, 2019 - 13:48

OT: Just curious, what exactly are the concerns on compatibility with different distributions? By running the unofficial build of shoogle (https://github.com/musescore/MuseScore/pull/5200) it works without any problems for me (OpenSuse Leap).
I don't think, that it would solve the behavior of empty palettes, but at least it would fix the "dead keys" issue.

mtuliosax

• Oct 11, 2019 - 00:18

I downloaded shoogle's build. It works fine in my system. However it uses old style palettes.

mike320

• Oct 11, 2019 - 00:52

The new palette styles have not yet be officially released.

mtuliosax

• Oct 11, 2019 - 04:33

I know it. Follow the discussion. The scope is to figure out the issue involving (blank) new palettes.

dmitrio95

• Oct 14, 2019 - 09:56

See this discussion. Basically, the concerns were about building AppImage based on Ubuntu 18.04 while using Ubuntu 16.04 didn't seem possible because some libmir* dependencies were required in that case. It looks like @shoogle was able to work around that in his PR but that PR largely changes the entire AppImage building process and still needs testing.

Jojo-Schmitz

• Oct 31, 2019 - 15:35

See #296082: Palettes completely invisible and unusable in Ubuntu 18.04, using AppImage

woozl.1986

• Feb 28, 2020 - 00:33

If you have an empty palette in ubuntu (maybe works in other distros, too), try to install these files: qml-module-qtquick-controls2; qml-module-qtquick-window2; qml-module-qtquick2; qml-module-qtgraphicaleffects; qml-module-qtqml-models2

I hope it works for you, too

oscarcar

• Oct 21, 2021 - 20:43

Thank you! This was the missing piece.

ValerieDicusar

• Aug 25, 2022 - 13:48

If you are using a mac you can press fn + shift + f9 then it should appear

Marc Sabatella

• Aug 25, 2022 - 14:12

Actually you shouldn't need Shift - that's only for the special-purpose "master" palette intended for customization purposes, not the standard palette intended for normal use. Just plain Fn+F9 is all you need for the standard palette. Fn is not Mac-specific, but on any computer that uses the function keys for multiple purposes, if the computer is configured to do the other purpose by default. Most computers can be configured either way - so that F9 by itself is really F9 and you need Fn to change speaker volume or whatever the dual function is.