How to remove old version of MuseScore from Chromebook

• Dec 7, 2019 - 01:56

I used the "install" option to put MuseScore on my Chromebook. No problems and everything works fine. However I now have three different versions of MuseScore and would like to remove the oldest version. How do I remove the old versions?


In reply to by Shoichi

This is good information, but, unfortunately it does not work with an AppImage that has been "integrated" into Chromebook. With the MuseScore AppImage, once you have used the chmod +x command to make it executable, you can run MuseScore from the terminal with the command (using version 3.3.4 as an example):


That command will let you to test and make certain that MuseScore is working on your ChromeBook. If you decide not to keep MuseScore, then you can simply delete the AppImage file and everything is back to where it was before you began. But, If everything is working fine you can install MuseScore using the "install" option shown below.

./MuseScore-3.3.4*.AppImage install

When you use the "install" option, MuseScore will the application is integrated into your system and you no longer will need to start it using the Terminal command. An icon will be created that will let you run MuseScore the same as you do any other program on your ChromeBook. In fact if you then delete the MuseScore AppImage file, MuseScore is still installed on your ChromeBook!

However, there is a problem with deleting the AppImage file - you cannot remove the installed MuseScore using the normal Linux commands. To remove the program you must run the AppImage from the terminal and use the "remove" option:

./MuseScore-3.3.4*.AppImage remove

The great developers at MuseScore are good about releasing updates and I like to try the updates before I remove the previous versions. In my case, I had three fully operational versions of MuseScore running on my ChromeBook. After each install, I had deleted the AppImage file to keep my "Download" directory clean and manageable. That meant that I could not remove the old versions of MuseScore since the normal Linux commands do not work.

My solution has been to create a new folder under Linux named "AppImages". When I download a new AppImage, I save it in this folder instead of the Downloads folder. This lets me keep my Downloads folder clean. At the same time I keep all of my AppImage files neat and organized in the same place. I do not delete an AppImage file until after I have run it using the "remove" option. This way I can maintain my ChromeBook clean and neat.

If you mistakenly delete an AppImage file before you remove an old copy of MuseScore, you can re-download the old version from the file archives on Then you can chmod +x the AppImage and run it with the "remove" option to get rid of the old install.

NOTE: to remove an old installed copy, the AppImage file must be in the same directory as the original. That is why I created a folder name "AppImages". Now I do not have to trust my memory about which folder I installed from.

I'm still experimenting with this myself and don't have all the answers, but I have some insight from my experience so far.

First, I assume you are referring to the AppImage. The location to which it was installed depends on whether you ran with "sudo" or not. If so, it's in /usr/local/bin, otherwise it's ~/.local/bin. You should see the AppImage files have been copied there, and you can safely just delete the ones you no longer need. You would also want to delete the originals - the file you downloaded, presumably to your Downloads folder or wherever else you downloaded to.

I would say you can run the older AppImages with the "uninstall" option, but I would guess this will actually have the effect of removing some of what's still necessary for your current version (e.g., the desktop file in share/applications under either /usr/local or ~/.local). In the future, you could run the uninstall before the next install. This seems to work well enough except it may or may not clean up some symbolic links.

BTW, I finally got a Chromebook that can use the official Linux app support a few weeks ago, and so far I have found and fixed a few issues that seem unique to that installation. As of 3.3.4 (current as of this writing, released a couple of days ago), it seems to be functioning as well as on my Windows computer. There are a small handful of installation-related things I still need to do by hand, and not all of them are working perfectly. Wondering if you've encountered the same and have found solutions.

1) the default installation makes MuseScore the handler for a number of MIME types but it doesn't appear to set things up fully enough for ChromeOS to see it, so double-clicking a score from the ChromeOS "Files" app doesn't work. I found I can fix this by manually fiddling with the MIME info, but I don't know what I'm doing, so its been trial and error. Adding application/x-musescore and application/x-musescore+xml to the list of MIME types in the "mscore-portable.desktop" file mostly fixes this, but somehow some MSCZ files still won't associate with MuseScore and I don't understand why. Running update-mime-database helps, but I'm still not really clear on how I should be doing this.

2) ChromeOS normally reserves Alt+Up/Down as page up/down, and I can't find a way to defeat that. I use those shortcuts in MuseScore a lot, so I tried redefine these shortcuts in MuseScore to be Alt+[ and Alt+], but ChromeOS seems to reserve these too. That much apparently can be defeated from the Linux side by editing some config file or other, but I decided it wasn't worth it to me, and just used [ and ]. Similarly, Alt+Shift+Up/Down create conflicts, but here Alt+Shift+[ and Alt+Shift+] work fine.

3) The title bars of Linux apps are blank, this is annoying but not specific to MuseScore and apparently there isn't anything to be done about it.

These are really quite minor considerations, though, and overall I am extremely pleased with how MuseScore runs as a Linux app on ChromeOS.

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