RSS feed for linux nightly build is published too early

• Aug 6, 2014 - 09:12

Reading the last RSS feeds for mscore "…" told me that a new nightly build is available. But after downloading, the zipped tar.bz2 file seems to be shortened and therefore corrupt.

Ergo: the RSS news should not be published before the generation of the tar.bz2 file is complete.


The only solution I see for now is to adjust the script that generated the rss to take into account the creation timestamp of the file. If younger than lets say 10 minutes, discard it.

I'll let you know when the fix is in place.

In reply to by Thomas

it's a compilation problem. The uploaded file contains the same file which has been compiled on my computer. This file is too short. Recent file is 293,3 Mio, old one is 321Mio.

... and.... launching the old or the recent I receive
error while loading shared libraries: cannot open shared object file: No such file or directory
however the requested lib is in
and in
and my path is
leleu@leleu-portable:~/musescore/MuseScore > echo $PATH

obviously the path is erroneous. I try to fix

In reply to by robert leleu

Just to be sure, can you try to launch
ldd mscore
and see if it finds all the correct libraries?

Is it just a typo in the previous message the discrepancy between ~/Qt5/5.3/gcc_64/bin and the one in the path: ~/Qt5/5.3.1/5.3.1/gcc_64/bin ? (Or maybe you simply created a symbolic link to the folder)

You could try to follow this workflow: to check if some libraries are loaded wrongly (for example, the wrong version).

The error you get is very similar to the one I have in Windows when a Nightly build is trying to load the platform plugin from a different Qt installation (which is now solved with the qt.conf file).

Hope this helps.

EDIT: I see you have already commented on the PATH, sorry for the noise :-)

In reply to by ABL

ldd mscore2 => (0x00007fff48b1f000) => /lib64/ (0x0000003c03800000) => /lib64/ (0x000000370c800000) => /lib64/ (0x0000003c00800000) => /lib64/ (0x0000003f8ae00000) => /lib64/ (0x0000003f8b600000) => /lib64/ (0x0000003f8c800000) => /lib64/ (0x0000003f8d000000) => /lib64/ (0x00007effd2908000) => /lib64/ (0x0000003f8cc00000) => /lib64/ (0x0000003f8be00000) => /lib64/ (0x0000003f8e200000) => /lib64/ (0x0000003f8f600000) => /lib64/ (0x0000003f91e00000) => /lib64/ (0x0000003be7c00000) => /lib64/ (0x0000003be7000000) => /lib64/ (0x0000003be7400000) => /lib64/ (0x0000003380e00000) => /lib64/ (0x000000365f400000) => /lib64/ (0x0000003be7800000) => /lib64/ (0x0000003f8d800000) => /lib64/ (0x00007effd22e3000) => /usr/local/lib64/gcc/ (0x00007effd1fd9000) => /usr/local/lib64/gcc/ (0x00007effd1dc1000) => /lib64/ (0x0000003be6c00000) => /lib64/ (0x0000003c00400000) => /lib64/ (0x0000003bffc00000) => /lib64/ (0x0000003c07600000) => /lib64/ (0x000000370c000000) => /lib64/ (0x0000003c08200000) => /lib64/ (0x0000003be9000000)
/lib64/ (0x0000003be6800000) => /lib64/ (0x0000003705e00000) => /lib64/ (0x0000003705a00000) => /lib64/ (0x0000003c04000000) => /lib64/ (0x0000003989400000) => /lib64/ (0x0000003bed400000) => /lib64/ (0x0000003be9c00000) => /lib64/ (0x00000037a4e00000) => /lib64/ (0x0000003704e00000) => /lib64/ (0x000000365c800000) => /lib64/ (0x0000003986c00000) => /lib64/ (0x0000003d55800000) => /lib64/ (0x0000003b92c00000) => /lib64/ (0x0000003beb000000) => /lib64/ (0x0000003a31400000) => /lib64/ (0x0000003a30c00000) => /lib64/ (0x0000003836000000) => /lib64/ (0x0000003837c00000) => /lib64/ (0x000000374f000000) => /lib64/ (0x000000358c200000) => /lib64/ (0x0000003294600000) => /lib64/ (0x0000003290600000) => /lib64/ (0x0000003989000000) => /lib64/ (0x0000003e4f800000) => /lib64/ (0x0000003e51000000) => /lib64/ (0x0000003e4fc00000) => /lib64/ (0x0000003e50c00000) => /lib64/ (0x0000003e50800000) => /lib64/ (0x0000003e50400000) => /lib64/ (0x000000377dc00000) => /lib64/ (0x00007effd1b74000) => /lib64/ (0x0000003f8e600000) => /lib64/ (0x0000003f8f200000) => /lib64/ (0x0000003f8de00000) => /lib64/ (0x000000337f600000) => /lib64/ (0x000000358b600000) => /usr/lib64/pulseaudio/ (0x000000365f000000) => /lib64/ (0x0000003c37800000) => /lib64/ (0x0000003c00c00000) => /lib64/ (0x00000037a5200000) => /lib64/ (0x0000003705200000) => /lib64/ (0x0000003a31800000) => /lib64/ (0x0000003bf1000000) => /lib64/ (0x0000003f76e00000) => /lib64/ (0x0000003f77200000) => /lib64/ (0x0000003bf3800000) => /lib64/ (0x0000003be9800000) => /lib64/ (0x000000365cc00000) => /lib64/ (0x000000365c400000) => /lib64/ (0x0000003bf2c00000) => /lib64/ (0x0000003bf5c00000) => /lib64/ (0x0000003987000000) => /lib64/ (0x0000003b0d800000) => /lib64/ (0x0000003986400000) => /lib64/ (0x0000003a30000000) => /lib64/ (0x0000003a2fc00000) => /lib64/ (0x0000003bf1400000) => /lib64/ (0x0000003a30800000) => /lib64/ (0x0000003d54800000) => /lib64/ (0x0000003d55000000) => /lib64/ (0x0000003bf7400000) => /lib64/ (0x0000003d55400000) => /lib64/ (0x0000003beac00000) => /lib64/ (0x000000328d200000) => /lib64/ (0x0000003beb400000) => /lib64/ (0x0000003be9400000) => /lib64/ (0x0000003c07a00000) => /lib64/ (0x0000003e50000000) => /lib64/ (0x000000337fe00000) => /lib64/ (0x000000337fa00000) => /lib64/ (0x0000003bee800000) => /lib64/ (0x0000003efae00000) => /lib64/ (0x000000302ae00000) => /lib64/ (0x000000365e800000) => /lib64/ (0x000000365ec00000) => /lib64/ (0x0000003c09600000) => /lib64/ (0x0000003c09a00000) => /lib64/ (0x0000003bfe800000) => /lib64/ (0x0000003bea000000) => /lib64/ (0x0000003986000000) => /lib64/ (0x0000003d54c00000) => /lib64/ (0x0000003e68800000) => /lib64/ (0x0000003efaa00000) => /lib64/ (0x0000003029800000) => /lib64/ (0x0000003bfe000000) => /lib64/ (0x0000003bfe400000) => /lib64/ (0x0000003c03400000)

In reply to by Joachim Backes

@Joachim Backes : I'm sorry, I should have pointed out that my previous comment was intended for robert leleu, i.e. the maintainer of Linux Nightly build, to try to solve his problem.
Do you see a crash at startup similar to his? In principle, from the log, it seems that mscore is loading all the needed libraries, in your case.

...I must remember to use @nickname more often in the future when posting in the forum...

In reply to by robert leleu

@robert leleu
It doesn't seem wrong. It is loading the Qt libraries from folder /home/leleu/Qt5/5.3/gcc_64/lib/.
Do you still see the crash at startup?

Have you compiled MuseScore again after correcting the PATH?
Inside the Makefile the folder ${HOME}/Qt5/5.3/gcc_64/bin is added in front of the PATH, so in principle there should not have been problems even if the PATH was wrong at compilation time.
If you still see the crash, can you try to compile again, removing the folder /home/leleu/Qt/5.2.0/gcc_64/bin from the PATH?

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