Crash when selecting View->Synthesizer in latest nightly

• Jan 23, 2014 - 22:04
S2 - Critical

Version used:…
On Ubuntu 13.10.
Crash immediately when "Synthesizer" is clicked.

Terminal output:
User@User-laptop:~/Downloads$ ./mscore
QDateTime("") QDateTime("")
Can't open '/usr/local/share/mscore-2.0//sound/aeolus/stops/Aeolus/definition' for reading
Can't open '/usr/local/share/mscore-2.0//sound/aeolus/stops/Aeolus/presets' for reading
ChordList::read failed:
loop toggled 0 - 0
Alsa_driver: stat = 00, xrun of at least 7552.411 ms
./mscore: symbol lookup error: ./mscore: undefined symbol: _ZN7QWidget21createWindowContainerEP7QWindowPS_6QFlagsIN2Qt10WindowTypeEE


Have you successfully run previously nightlies on this machine before? Trying to make sure you've got the necessary environment set up. Seems like maybe you haven't set up the installation folders properly.

I haven't run any! The only modification I did was to point musescore to the soundfont dir to enable playback.
Are there any instructions on the folder structure?

[Besides, I think the program should not crash but display a warning]

Thanks for the help.

Status (old) active needs info

Not crashing would be good, but this situation would never happen in "real life" - only during incomplete installations of experimental builds. There's probably any number of other errors that are not checked for that would normally never happen. So it's kind of a fact of life that nightly builds will crash sometimes when installed correctly; it's just not worth it to check for every possible strange thing that could go wrong if the installation is corrupt.

Of course, I don't even know that this is why it's crashing, but it's definitely why you get the console output you get, so it's as good a place as any to start.

I'm not sure how to correctly set up the folder structure - you might try to Technology Preview forum for help. If/when you get all that set correctly - and you'll know because the console output stops complaining about missing chordlist and aeolus files - then if it still crashes, come back and change the status of this back to "active" and see if perhaps there is more information you can provide that would help isolate the problem.

Cannot test right now. But as Marc pointed out - this is likely to only occur during testing of nightly builds when all the folders aren't set up correctly.

Also, this is quite old. While working with the nightly builds, the crash has not occured since.

Severity S2 - Critical
Status (old) needs info closed
Status needs info closed

Crashes are critical, but this one here got to be resolved since a long time, as Aeolus got disabled a long time ago