Palletes in the Workspace not showing

• May 9, 2020 - 22:44

The side menu titled "palettes" is currently showing nothing and I can't seem to add anything to it. The menu is completely blank. I can do stuff to the sidebar, such as close it and detach it from the program in it's own window. I can still use the Master Palette as well, and it works fine, but it's a hassle using it instead of the side menu palettes. I don't know how to fix the issue.

Attachment Size
Screenshot (6).png 43.26 KB

Comments

In reply to by Jm6stringer

I have the same problem and the factory reset didn't work. Tried it on both the current release as well as the development version (3.5).

When starting Musescore through the command line, these are the lines that I think could be related to it:

unknown:unknown: Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:unknown: qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:190:9: QML MenuSeparator: Binding loop detected for property "implicitHeight"
qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:unknown: qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:177:9: QML MenuSeparator: Binding loop detected for property "implicitHeight"
qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:unknown: qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:170:9: QML MenuSeparator: Binding loop detected for property "implicitHeight"
qrc:/qml/MuseScore/Palette/PaletteTree.qml:unknown: qrc:/qml/MuseScore/Palette/PaletteTree.qml:178: Error: Cannot assign to non-existent property "color"
qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:unknown: qrc:/qml/MuseScore/Palette/TreePaletteHeader.qml:190:9: QML MenuSeparator: Binding loop detected for property "implicitHeight"

This goes on for a while.

I'm on Manjaro KDE and installed Musescore through the musescore-dev AUR package.

Really hope this gets fixed. It used to work, even on a 3.x version, but after some update (I use Musescore irregularly so I'm not sure which one), it started happening. See screenshot below.

Attachment Size
Screenshot_20200729_174454.png 76.08 KB

Do you still have an unanswered question? Please log in first to post your question.