MuseScore AppImage fails to start

• Apr 28, 2020 - 22:37
Reported version
S2 - Critical
needs info

Dowloaded the ApplImage to my Fedora 31 system, all updates are current.

Upon execution I get the following:

$ ./MuseScore-3.4.2-x86_64.AppImage
[paul@localhost ~]$

Program immediately exits.


Frequency Once Many
Severity S2 - Critical S1 - Blocker
Reported version 3.4 3.6

I'm getting the same thing on Linux Mint Cinnamon 19.2, and it doesn't appear to be related to #292037 as far as I can tell.
After downloading the 64-bit AppImage for Linux, I "chmod 755" the file, then try to run it, and get the same results each time (the program immediately exits without opening any window):

$ ~/Downloads/MuseScore-
$ ~/Downloads/MuseScore- -F
$ ~/Downloads/MuseScore- -w
$ ~/Downloads/MuseScore- -s

Thinking that maybe I needed to manually install these, I tried "sudo apt-get install libjack-dev libnss3-dev", but still got the same results.

I also tried building using cmake and Qt5.15.2, but had a heck of a time getting Qt to work since it complained about missing libraries, so I gave up on building from source.

Frequency Many Few
Severity S1 - Blocker S2 - Critical
Reported version 3.6 3.4

Still a duplicate, Go to #292037: MuseScore AppImage crash when change settings to JACK or from JACK instead, this one here is a dead end road
If it isn't #292037: MuseScore AppImage crash when change settings to JACK or from JACK, it isn't this one here either and a new issue would be needed

I am building 3.x using Qt 5.15.2 since long and have no problems with it.

Title Failed to start MuseScore AppImage fails to start
Status duplicate active

Hmm, maybe it isn't a duplicate after all, as here no crash seems to be happening?

Status active needs info

Try the "-d" option to see if you get more useful output. AppImage works fine for me and others, and I'm not aware of any other specific reports of the AppImage simply exiting with no message. So we'd need more information to understand what unique qualities of your particular system are preventing it from working for you.

The messages you are seeing are perfectly normal, those are libraries where we use the installed library if available, so it's just a heads up, not an error.