In order to help, we would need you to attach the score you are having problems with and precise steps to reproduce the problem. Is the problem reproducible, or wasd it a one-time thing? I realize posting the score might be tricky if it crashes when you save, but more information would help - is this a score you just created, one created earlier that you just edited slightly, or what? Does it work if you do "Save As"? How about "Save Online"? And what OS are you on?
i am not used to scribe in English so...
my os is Linux mint 17 64bit
i have installed Musescore 2,0,3
when the problems occur, i have it with the most of my scores, when i klik save it crashes.
if i try another one it crashes too, so i do not think the problem is related to one specific score or one specific change. when i change de title en klik save it crashes. change something else, it crashes ons save.
on my linux machine i have virtual box with windows 7 installed 32 bit with musescore 2,0,1.
When in try to open the same score in that version it works flawless.
most of my scores i receive in a xml format and after modifying i save it as a mscz file.
most of the time the loading af a xml file gives an error bit ingnoring that the file opens.
Save as seems to be working.
My best guess is that there is some score in your "recent files" list that is corrupt and causing a crash when MuseScore tries to read or generate a thumbnail. Try Help / Revert to Factory Settings, and try working on just one score for a while to see if you have problems, if not, try another, etc.
I am having the same problem with a newly installed copy of musescore (on archlinux), so it is NOT "... some score in your "recent files" list that is corrupt ..." This is a bug in the current version of musescore. As it stands. musescore 2.0.3-2 is completely unusable. Is anyone working on this? Is there any known work around?
I am facing the same problem as well, using version 2.0.3., rev. 3c7a69d, OS ubuntu 16.04.
it is not strictly reproducable, but it happens quite often, i.e. when saving existing files to a new filename, but also with new files.
Have you tried Help / Revert to Factory Settings as suggested above?
If that doesn't fix it, then I will guess this happens only for some specific score. Probably it is corrupt in some way. You were able to load it, then you did some edits, and it crashed trying to save the edited version? If so, please attach the unedited version of the score and give us steps to reproduce the problem.
It crashes with all the scores I've tried, including 'my_first_score'.4
I've attached the 'my_first_score' template, 'my_first_score2.mscz' (created just now when testing the template) and 'Ionisation part 2.mscz' - all of which crash within a few seconds of saving, whether or not I write or change any notes.
I'm running MuseScore 2.0.3 rev 3c7a69d. The Ionisation file was an older one, but I haven't been able to save it since.
I've attached two LibreOffice files with Terminal output. First is the output from simply running 'mscore'. I've also attached the output from running 'mscore' from the Terminal, then saving 'my_first_score' in the MuseScore GUI.
I couldn't run mscore with administrator privileges (I tried 'sudo mscore' and 'sudo su' followed by 'mscore'. Instead I got:
No protocol specified
QXcbConnection: Could not connect to display :0
Aborted (core dumped)
Kuwitt - running mscore after 'su' is the same:
[root@localhost Adam]# mscore
No protocol specified
QXcbConnection: Could not connect to display :0
Aborted (core dumped)
[root@localhost Adam]#
Jojo-Schmitz - I've read through the linked files, and tried saving again after deleting ~/.local/share/data/MuseScore/MuseScore2/session and ~/.local/share/data/MuseScore/MuseScore2/plugins
The crashes still happen.
Got the same issue, removed musescore using standard apt-get command, and use now the appimage successfully.
Then Musescore displays a 2.1 version when I was previously running 2.0.3
Comments
In order to help, we would need you to attach the score you are having problems with and precise steps to reproduce the problem. Is the problem reproducible, or wasd it a one-time thing? I realize posting the score might be tricky if it crashes when you save, but more information would help - is this a score you just created, one created earlier that you just edited slightly, or what? Does it work if you do "Save As"? How about "Save Online"? And what OS are you on?
i am not used to scribe in English so...
my os is Linux mint 17 64bit
i have installed Musescore 2,0,3
when the problems occur, i have it with the most of my scores, when i klik save it crashes.
if i try another one it crashes too, so i do not think the problem is related to one specific score or one specific change. when i change de title en klik save it crashes. change something else, it crashes ons save.
on my linux machine i have virtual box with windows 7 installed 32 bit with musescore 2,0,1.
When in try to open the same score in that version it works flawless.
most of my scores i receive in a xml format and after modifying i save it as a mscz file.
most of the time the loading af a xml file gives an error bit ingnoring that the file opens.
Save as seems to be working.
and it gets worse.
musescore crashes a few minutes after opening.
for no apparent reason
My best guess is that there is some score in your "recent files" list that is corrupt and causing a crash when MuseScore tries to read or generate a thumbnail. Try Help / Revert to Factory Settings, and try working on just one score for a while to see if you have problems, if not, try another, etc.
I am having the same problem with a newly installed copy of musescore (on archlinux), so it is NOT "... some score in your "recent files" list that is corrupt ..." This is a bug in the current version of musescore. As it stands. musescore 2.0.3-2 is completely unusable. Is anyone working on this? Is there any known work around?
I am facing the same problem as well, using version 2.0.3., rev. 3c7a69d, OS ubuntu 16.04.
it is not strictly reproducable, but it happens quite often, i.e. when saving existing files to a new filename, but also with new files.
I have the same problem using MuseScore 2.0.3 rev 3c7a69d on Fedora 25. It happens every time I try to save or 'save as'.
Have you tried Help / Revert to Factory Settings as suggested above?
If that doesn't fix it, then I will guess this happens only for some specific score. Probably it is corrupt in some way. You were able to load it, then you did some edits, and it crashed trying to save the edited version? If so, please attach the unedited version of the score and give us steps to reproduce the problem.
Reverting to factory settings didn't help.
It crashes with all the scores I've tried, including 'my_first_score'.4
I've attached the 'my_first_score' template, 'my_first_score2.mscz' (created just now when testing the template) and 'Ionisation part 2.mscz' - all of which crash within a few seconds of saving, whether or not I write or change any notes.
Any thoughts very gratefully received!
Thanks
First of all upgrade from 2.0.1 to 2.0.3. ("Ionisation part 2.mscz" apparently was written or at least last saved with 2.0.1)
Could you please run MuseScore from terminal and write down the whole output here?
Check also, if you've a crash, when you run MuseScore with administrator permissions, maybe a case of writing permissions (?).
Thanks for the speedy response.
I'm running MuseScore 2.0.3 rev 3c7a69d. The Ionisation file was an older one, but I haven't been able to save it since.
I've attached two LibreOffice files with Terminal output. First is the output from simply running 'mscore'. I've also attached the output from running 'mscore' from the Terminal, then saving 'my_first_score' in the MuseScore GUI.
I couldn't run mscore with administrator privileges (I tried 'sudo mscore' and 'sudo su' followed by 'mscore'. Instead I got:
No protocol specified
QXcbConnection: Could not connect to display :0
Aborted (core dumped)
Enter "su", then entering the password, then running "mscore" doesn't work too?
Hmm,
*** Error in `mscore': free(): invalid pointer: 0x0000560198159980 ***
This looks familiar, see #180131: crash on ubuntu 16.04
Kuwitt - running mscore after 'su' is the same:
[root@localhost Adam]# mscore
No protocol specified
QXcbConnection: Could not connect to display :0
Aborted (core dumped)
[root@localhost Adam]#
Jojo-Schmitz - I've read through the linked files, and tried saving again after deleting ~/.local/share/data/MuseScore/MuseScore2/session and ~/.local/share/data/MuseScore/MuseScore2/plugins
The crashes still happen.
Which desktop enviroment are you using? I guess KDE?
Try to start MuseScore with another window-manager (like XFCE, LXDE, Cinnamon or another)
If this doesn't work, try to start the AppImage:
https://musescore.org/en/download#AppImage
Ask also your support request in a Fedora-forum.
Last but not least: Please response, if you find a solution.
I'm using Gnome 3.22.2. I've tried running MuseScore in Cinnamon, but it still crashes.
But I removed MuseScore using dnf, then installed the AppImage and it seems to work OK - no crashes so far!
Many thanks for all your help and suggestions.
In reply to #17 by AdamCWB@btinte…
Got the same issue, removed musescore using standard apt-get command, and use now the appimage successfully.
Then Musescore displays a 2.1 version when I was previously running 2.0.3
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.