crash on startup

• Aug 16, 2014 - 21:36

Just downloaded latest 32-bit nightly for Ubuntu, which crashed during startup (return code 134). I'm happy to provide more details if someone tells me how. Here is the output from the command line:

(0)[dcarson@eagle musescore] ./mscore
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
Fluid: sf  not found
Internal error: shortcut  not found
name2type: invalid type 
: xml read error at line 1133 col 29: AccidentalBracket
Aborted (core dumped)
(134)[dcarson@eagle musescore] 

I have the core file, which is 114MB, if someone wants it.


(0)[dcarson@eagle musescore] uname -a
Linux eagle 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:49:09 UTC 2014 i686 i686 i686 GNU/Linux
(0)[dcarson@eagle musescore] 
(0)[dcarson@eagle musescore] lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.1 LTS
Release:	14.04
Codename:	trusty 




In reply to by Jojo-Schmitz

...did the trick. Thank you.

I'm not very familiar with using the nightlies, so I didn't think about the fact that I had done so a few months back. Usually, I use the released 1.3 version.

I am right in assuming that the 1.3 version and whatever flavor of 2.0-nightlies I chose will not interfere with each other -- unless of course I try to use an output file from one in the other -- correct?

In reply to by dccarson

You are correct. And actually, 1.3 files should open fine in 2.0 - file an issue if you have one that doesn't. But the reverse is not true. So don't take a 1.3, open it in 2.0, and then save it expecting to take it back to 2.0. If you try to save a file loaded form 1.3, MuseScore will prompt you for a new filename to discourage you from overwriting the original. Take the hint :-)

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