Musescore Appimage
Hey, I wanted to tell you about a bug I'm having when using AppImage Musescore on my HP Chromebook x360 with an Intel Core i3 8th generation. Whenever I click the icon on the taskbar, or when clicking the finish button when creating a score, the screen blacks out and closes musescore. How do I fix this?
Comments
Which version of Chrome OS are you running? Version 81 that was just released a few days ago broke Linux apps pretty badly. There is a partial workaround of going turning off GPU acceleration (?) by going to your browser, typing chrome://flags in the address bar, and searching for "crostini-gpu-support" and disabling it. This fixes most of the glitches I was seeing, although some remain, like sometimes I can't type into file dialogs. Again, it's a general issue with Chrome OS and all Linux apps.
If you're still on Chrome OS 80 or earlier, though, it should work well, so we'd need more info. Like which version of MuseScore, and is it fixed if you try Help / Revert to Factory Settings. Also is your Linux container "stretch" or "buster" (was it created before ChromeOS 80?)
In reply to Which version of Chrome OS… by Marc Sabatella
It's version 81, and turning off GPU acceleration didn't work, and it's the newest version of Musescore, although I don't know where to find stretch/buster.
In reply to It's version 81, and turning… by PhoneyAlabama
To be honest I'm not sure either, but if you created the Linux container prior to Chrome 80, it defaults to stretch, if you did it with 80 or 81, it defults to buster. I'm on stretch. Those are just that Linux (debian specifically) uses instead of version numbers.
Did you try the revert to factory settings, then? BTW, you say it's the newest version of MuseScore, but that could mean something different depending on how/when you downloaded it. Could you check Help / About and be sure it says 3.4.2?
In reply to To be honest I'm not sure… by Marc Sabatella
It is 3.4.2, also do you mean reset Musescore's factory settings?
In reply to It is 3.4.2, also do you… by PhoneyAlabama
Yes, as I said, in the Help menu. Just because some crashes like you describe turn out to be issues with the installation or settings or older scores stuck somewhere that the revert solves.
In reply to To be honest I'm not sure… by Marc Sabatella
I have the same problem. Chrome OS is up-to-date. Linux Container is "Buster". I'v installed software following the official video tutorial. What can I do?
In reply to I have the same problem… by tecnologiemusicali
Mostly, wait for Google to fix this showstopper bug in ChromeOS, I'm afraid. Although the specifics of the bug seem to vary across systems. I'm working with a couple of Google engineers to make sure they can reproduce the problem as it exists on my system. For me the crashes are much more sporadic but I do have a way I can make it happen reliably, using a particular AppImage from a point a couple of weeks ago in the MuseScore 3.5 development. The released 3.4.2 AppImage almost never triggers the problem for me.
Make sure you have alsa-utils installed, btw. Apparently this can sometimes get uninstalled as part of the updates, and this will prevent MuseScore from starting (no crash for me, it just hangs).
In reply to Which version of Chrome OS… by Marc Sabatella
I'm having the same problem, but resetting to factory settings isn't helping.
In reply to I'm having the same problem,… by iyhn8192
Same problem here too.
In reply to Same problem here too. by Saxswan
The ChromeOS bug that causes this crash is fixed in version 83, so updating should fix it. Also, you can prevent it by making sure you run the "install" step on the AppImage.