Musescore crashing after startup on new install

• Jun 6, 2020 - 18:48

I am trying to get to be able to use MuseScore on my Chromebook. I followed the installation directions from this page exactly: https://musescore.org/en/handbook/install-chromebook
Setting up the Linux install worked fine. I did have to run the given sudo lines because of missing packages, but those installed OK and I got no errors when trying to start MuseScore after that. I selected the option to have tours offered, but when I got to the first dialog box where I had to hit "Next" for the tour, the chromebook crashed and restarted. The next time I opened MuseScore I hit "Cancel" instead of "Next", thinking that maybe the problem had to do with the tour. But when I clicked on the "Create New Score" button, the chromebook crashed again and restarted. The next time, I hit cancel for the tour, cancel on the "Create New Score" window, and the chromebook crashed and restarted. So, it seems like no matter how I get to the main application window, when I do, the chromebook crashes. It is not caused by any specific score, because I haven't gotten to the point of even creating a blank score. Oh, and when I launch MuseScore again, after a crash, it asks me whether I want to restore the previous session or not. No matter whether I choose to restore or not, the application crashes. I am on a chromebook with an Intel processor, and I just installed Linux to be able to use MuseScore, I haven't done anything to configure it any differently except install the two packages needed for MuseScore and listed on the https://musescore.org/en/handbook/install-chromebook page. From another forum post, it sounded like it might be relevant what linux version, so I checked, and it is "buster".


Comments

Be sure not to skip the "install" step from those instructions, it works around a bug in Chrome OS 81 that caused crashes. It is also just generally nice, as it allows you to start from the launcher, get a program icon, pin it to the shelf, etc.. But the bug is fixed in Chrome OS 83, so updating that should fix it too.

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