any ideas about what could cause crash when open from inside musescore, while not crashing when open from outside?
I have a friend using an Lubuntu labtop I setup for him a year and a half ago, running 2.0.3. He has had a strange problem of not being able to open a file from within the software, and so instead has to open files from documents folder outside of muse score in order to prevent it from freezing.
Also, says when try to split a score into parts it freezes. It also freezes when try to rename a part after right clicking to get into staff properties.
I'll probably have to physically use his computer and run musescore from qtcreator to see what happens. But I was wondering if someone has any possible ideas about what could be going on.
Comments
One thing I would try would be to use another window manager (for example XFCE - Lubuntu uses LXDE, right?) to proof whether the problem also occurs there.
Obviously, without seeing the score itself, we can only guess.. But as long as we're guessing, it's possible he has multiple versions of MuseScore installed, and opening from the file manager opens it in a version that doesn't have the bug.
In reply to Obviously, without seeing the by Marc Sabatella
I should have said that I have the score, and I'm able to use it just fine on my linux and windows machine. This freeze has occurred on his computer for the past couple months. The particular file is not at fault.
In reply to I should have said that I by ericfontainejazz
In Opensuse I also can load and work with this file without any problems (open it in Musescore, splitting it and so on).
So beside the choice of the Window manager/Desktop environment does he use the ubuntu package or the api image, which hardware does he use (maybe a lack of memory?), is there none error message, when he starts Musescore from terminal?
So many possibilities ;-)
In reply to I should have said that I by ericfontainejazz
When I open this I see a bunch of error messages (involving hairpins) printed to the console. Form the looks of it, maybe these result in some invalid reference somewhere, that either crashes or not depdning on whatever happens to be going on in memory at the moment.
I'm just going to have to inspect his computer to get a better idea, but thanks.