[Flatpak] Apply new style button vanishes as soon Leland or Edwin is selected

• Feb 5, 2021 - 09:16
Reported version
3.6
Type
Graphical (UI)
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

I'm on Debian Buster x64 and use the musescore 3.6.1 flatpak.

If I open a score created with a musescore version <3.6 musescore asks if I would like to apply the new notation and text font.
As soon as I check one of them the Button "Apply new Style" vanishes and it doesn't come back, even if I uncheck all the boxes.

Okay. I just checked with the AppImage of musescore and there the button stays and I am able to click it. strange...

If more information is needed I am glad to provide them.

Best regards
Samuel


Comments

Status active needs info

As far as I know, it's a third party that provides flatpak and anything else other than AppImage. I believe this dialog is built with QML, my guess is they are building with the wrong version of some Qt library. This is something that would need to be reported to the maintainers of that build. Meanwhile, though, this is a big part of why we provide AppImage builds - it's really the only system we can control, test,t and support ourselves.

If the flatpak people report back that there is some makefile or other change that would facilitate their process, that's not to say we couldn't consider making this change. But we'd need to understand what they actually need.

On the github repository of the musescore flatpak, we found out, that there might be a problem with Qt 5.15.2. There are a lot of qml-Errors in the console.
Unfortunately im not confident how to investigate this further.

See https://github.com/musescore/MuseScore/pull/7388, esp. for fixing these warnings (they ain't errors, just deprecation warnings, still pretty annoying). Feel free to integrat that iinto yout Ftappak version, that is exactly why it is still open.
But note also that MuseScore 3.x generally is only tested and officially available with Qt 5.9.x (and that is why that PR hadn't been merged into 3.6.2)