Musescore-4.4.3.lp156-181.3.x86_64 not working

English Applications
1

Hi everyone.
Does anyone know why the above musecore version crashes everytime when starting? I have a machine on lp156 where it is not working at all, whereas on another machine with tumbleweed and musescore-4.4.3.181.5.x86_64 does load?
when starting “mscore” in the terminal there is a lot of output with errors, mostly qml related, but it is not clear which one is the fatal one.
unortunately, I cannot revert to a previous version because I use files from musecore.com, and then they won’t load and tell me to update to a higher version.
Has anyone experienced similar problems with the same version and solved it?
(please don’t tell me to upgrade to tumbleweed, I need different Opensuse versions incase of trouble like this, so I can still work when there is serios trouble with one version)

help appreciated, when you have experiences with musescore trouble!

Cheers, Cellocommander

2

output on the console:

3

First you need to explain from where you installed this package. The latest available version for Leap 15.6 is musescore-4.2.1-bp156.2.2 in the OSS repo.

4

https://build.opensuse.org/projects/multimedia:apps/packages/musescore/repositories/15.6/

5

As this is a development repo, you might open a bugreport that this package does not work on Leap 15.6.

Installing qt6-qt5compat-imports reduces the amount of errors, but mscore still does not start.

6

thanks for the repies!
does anyone know how to solve this?

7

Same here and when I search on the musescore sides, they say that musescore is build for qt 6.2 and not for qt 6.6…

8

Hi,
der root cause ist, dass sich die QT-Entwickler um Abwärtskompatibilität nicht scheren. Daher gibt es jetzt mit jeder neuen QT-Version (6) ständig Probleme. Ich kann mich noch grob daran erinnern, dass das mit der 5er Version kein Deut besser war - bis sie endlich irgendwann nicht mehr weiterentwickelt wurde und damit indirekt stabil wurde. Wenn die glibc-Programmierer genauso unterwegs wären, wäre Linux und alle anderen, die auf die glibc setzen, schon lange tot.

Ich habe das für mich jetzt so gelöst, dass ich die letzte musescore Version zur QT 5 mir selbst übersetze auf Basis des rpm Source-Pakets für tumbleweed (ich habe Leap 15.6).

Andere Variante ist, mit irgendeinem Flatpak - Gedöns oder Ähnlichem zu operieren, was sämtliche Abhängigkeiten mitbringt (oder statisches Linken). Das kommt mir allerdings nicht auf die Büchse. Da verliert man völlig die Übersicht, was man alles installiert / aktiv hat! Aus Sicherheitssicht für den Anwender die Totalkatastrophe - für den Entwickler natürlich ein Workaround, resultierend aus der Tatsache, dass die QT-Programmierer hinsichtlich Abwärtskompatibilität schlampen. Traurig.

9

Hey
English speaking Forum…

10

Ups - sorry. Unfortunately I can’t edit my post above. See below!

Hi,

the root cause is that the QT developers don’t care about backward compatibility. That’s why there are now constant problems with every new QT version (6). I can still vaguely remember that it was no better with the 5 version - until it was finally discontinued at some point and thus became indirectly stable. If the glibc programmers were the same way, Linux and all others that rely on glibc would have been dead a long time ago.

I have now solved this for myself by compiling the latest musescore version for QT 5 myself based on the rpm source package for tumbleweed (I have Leap 15.6).

Another option is to operate with some flatpak stuff or similar, which comes with all dependencies (or static linking). However, I wouldn’t put that on the box. You completely lose track of what you have installed / active! From a security point of view, this is a total disaster for the user - for the developer, of course, a workaround resulting from the fact that the QT programmers are sloppy when it comes to downward compatibility. Sad.

11

Maybe it’s a problem by the musescore developers not using an actual QT-lib…

You can see it as you will…

12

Mine works but only sound goes to PC speaker not the HDMI like all other programs - this is both the openSUSE version and Musescore Appimage - both sound to PC speaker and no other choice.

13

There shouldn’t be any dependency to a special version of a used library. Newer versions of (glibc, qt, …) must ensure, that programs using the old / previous versions have to work flawlessly, too. There are so many (old) C programs like inn or dhcpd or you name it, which work with actual glibc without any problem. Why? Because each new version of glibc is downward compatible.

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.