Musescore 3.4.2 on OpenSuse Leap 15.2: Palettes won't show up after update of operating system
Hi,
I am on OpenSuse Leap 15.2 and worked during the last couple of weeks with the 4.0.git20200620 version provided by the OpenSuse community. Everything was working fine. A few days ago I wanted to add something to an existing score and realized that the palettes window was empty. I uninstalled the version and installed the official release version 3.4.2 from OpenSuse, but this did not help. I tried everything I found in forums and search engines (reset to factory settings, start from command line etc.) but the palettes won't show up. There is a button to add palettes, but clicking on it only brings up the empty drop-down menu without any palettes.
When I start MuseScore from the command line I get the following errors:
qrc:/qml/palettes/PaletteTree.qml:152: Error: Cannot assign to non-existent property "color"
qrc:/qml/palettes/PaletteTree.qml:193:19: QML Component: Cannot create delegate
qrc:/qml/palettes/PaletteTree.qml: Object or context destroyed during incubation
The appimage of version 3.4.2 from the MuseScore Website works fine on my system, but for several reasons I would like to stick with the OpenSuse version.
Is there somebody else experiencing this issue? Is there a fix for this?
Thanks in advance for your answers.
Comments
There's probably some part of Qt missing
See also https://musescore.org/en/node/306817 which links to https://bbs.archlinux.org/viewtopic.php?pid=1910577#p1910577 which in turn mentions an issue with Qt 5.15, where downgrading to 5.14 helped
See also the just raised issue #307238: Palette is empty after some update + outputs errors
In reply to There's probably some part… by Jojo-Schmitz
Thanks, Jojo-Schmitz.
I read all the other posts and installed all the packages mentioned in the list, but no success, I'm afraid. My QT version is 5.12.7. Perhaps this is too old for this version of MuseScore.
One of the reasons why I wanted to use the OpenSuse version is that I use the dock program Docky because it's the only dock that really suits my needs. But it has problems with some appimages. I wanted MuseScore to show up in the dock so that I can see with a glance whether I have an open MuseScore window.
My workaround was to extract the appimage with
MuseScore-3.4.2-x86_64.AppImage --appimage-extract
and create a.desktop
file for MuseScore which points to theAppRun
file in the extracted folder. This way MuseScore shows up correctly in Docky and can also be started from there.In reply to Thanks, Jojo-Schmitz. I read… by lureli
No, 5.12.7 is not too old.
The default MuseScore gets build against is 5.9.x (x being 8 I think)
In reply to Thanks, Jojo-Schmitz. I read… by lureli
And I believe that running the AppImage with the install option (as mentioned in the instructions) should've given you that .desktop file as well.
In reply to And I believe that running… by jeetee
Thanks, jeetee!
I wasn't aware that there is an install option - it would have saved me a lot of time. Should have read the handbook...
I will try and see how it works.
In reply to And I believe that running… by jeetee
I tried the install. It creates a .desktop file that calls the copied appimage with the %F option, but when I start MuseScore, the window does not appear in Docky. So I think I will go with my workaround until I find out what is missing from my system preventing the OpenSuse version to run properly.
In reply to I tried the install. It… by lureli
Not sure if this will prove relevant, but on my system - a debian container running within ChromeOS - I needed to edit the Application line of the desktop file to read simply "MuseScore 3" instead of "MuseScore 3 Portable AppImage" or whatever. Otherwise, I could start it from my launcher but it would not display the correct icon on the shelf (taskbar) nor could I pin it.
I'm having the same problem with my Leap 15.2 System.
The funny thing is, that a new user gets the full palettes on the left as it should be.
On my own user profile, I deleted all MuseScore config files, but the palettes remains empty.
I suppose there is kind of attribute outside the MuseScore config itself.
In reply to I'm having the same problem… by stegruscore
Are you using the AppImage? Things in general should work there. Packages provided by third parties (including distribution maintainers) often have issues like this, which is one reason we provide the AppImage.
This has been reported today:
https://bugzilla.suse.com/show_bug.cgi?id=1179004
Seems to be a KDE bug.
In reply to This has been reported today… by deijnum
And a fix for openSUSE 15.2 will be released soon.