Musescore 2.0 Crash
Hello,
With Musescore 2.0, I have a problem:
http://nsa34.casimages.com/img/2014/05/16/140516092637815410.png
As soon as I start nightly.bat, it is similar also with nightly.exe...
Would need to repair this bug, that to make???
I have Windows XP Mo de RAM!
Bye for now!!!
Comments
2.0 does not exist yet, just the nightly previews, and these are to be discussed in the Techonoly Preview forum... ;-)
And there you'd Ned to give more details, like what did you do before the crash, what score, what exact version/commit etc.
Pretty recently there has been a change in the nightly builds that make it necessary to refer to factory default to get rid of some remnants of older builds.
In reply to 2.0 does not exist yet, just by Jojo-Schmitz
I moved the topic to the Tech Preview forum
In reply to Moved by Thomas
Thanks, see also #25762: mention possible need of a factory reset on the nightly builds' download pages
In reply to Thanks, see also #25762: by Jojo-Schmitz
Here is the version which I use: MuseScoreNightly-2014-05-16-1608-b9b5d20
And it is similar formerly :-(
In reply to Here is the version which I by Jajan
Did you try the factory reset?
In reply to Did you try the factory by Jojo-Schmitz
I made the reset (I did not know that there was), it re-works but unfortunately I have no more the black style which I had...
How to put back him? : http://www.fanordi.legtux.org/Sacha/bugmsn2.bmp
In reply to Problems styles by Jajan
The "-F" option clears your preferences. So you just need to go to Edit / Preferences and set them back how you like.
BTW, the leftover tab after closing a score is a known bug, we seem to assuming it's inherent in the Qt libraries MuseScore uses and will be fixed by them someday. I have no idea if any of that is actually true, though.
In reply to The "-F" option clears your by Marc Sabatella
Has an issue been filed reg. that leftover tab? For MuseScore and Qt?
In reply to Has an issue been filed reg. by Jojo-Schmitz
#21841: Score tab and navigator remains after closing a score here. Not sure about there, or if it really has conclusively been determined to be a Qt issue at all.