nightly build mscore.64bits-2014-08-04-14-34-25addca crashes immediately at start

• Aug 5, 2014 - 03:32

Trying to run the nightly build mscore.64bits-2014-08-04-14-34-25addca.tar.bz2 under Fedora20, but it creashes immediately because of:

./mscore: /lib64/ version `CXXABI_1.3.8' not found (required by ./mscore)
./mscore: /lib64/ version `GLIBCXX_3.4.20' not found (required by ./mscore)

On my box, libstdc++-4.8.3-1.fc20.x86_64 is installed.

Elder nightly builds don't show this misbehaviour.


In reply to by ChurchOrganist

Does not help, because as I told already, the binary will not start. "ldd mscore" shows the same error msg! I guess, mscore has been built with a gcc/g++ not compatible to the actual Fedora20 gcc which is gcc-4.8.3-1.fc20.x86_64, and it's libraries.

Is this correct?

In reply to by Joachim Backes

I could solve the problem by building and installing gcc-4.9.1 and using the correspondent libs. So my impression that the problem is a compiler problem seems to be intensified.

I'd expect some notice from the nightly builer people on the download page, that for the upcoming mscore-2.0 versions (on LINUX) a recent gcc version should be installed or used.

Kind regards

Joachim Backes

Since I upgrade to Mint17, compiled mscores crash, and I usually delete the uploads. I forgot to delete mscore.64bits-2014-08-04-14-34-25addca.tar.bz2.
gcc-4.9-base 4.9.1-3ubuntu2~14.04.1 , the last ubuntu version is installed
The compilation log shows no error. However the resulting mscore crashes as follows

leleu@leleu-portable:~/musescore/MuseScore/build.release/mscore > ./mscore >log
This application failed to start because it could not find or load the Qt platform plugin "xcb".

Reinstalling the application may fix this problem.

plugin 'xcb' is not in /home/leleu/Qt5/5.3/gcc_64/plugins/

According to synaptic libstdc++6 4.9.1-ubuntu2-14.04.1 is installed (the last version)
However I can't find any file whose name includes 'libst'

I've got the exact same issue here, with the mscore.64bits-2014-09-12-16-34-e2a6fbd.tar.bz2.
The 32bits-2014-09-11-1506-516d037.tar.bz2 doesn't work either, so far stuck on the older one.


In reply to by bartart3d

Generally speaking, if you've used an older nightly build, a crash on startup for a new one means you need to reset to factory settings - something in the palette or elsewhere changed incompatibly since the previous build. So mscore -F should always be the first thing you try if a nightly build crashes on startup.

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