Musescore 3 on a chromebook

• Dec 26, 2018 - 18:04

I have an ASUS Chromebook C223 running ChromeOS 71. I used the linux beta to install MuseScore through the terminal, but the latest version is 2.0.3. Is that the latest version for linux, is there a .deb file I can manually install somewhere, or am I doing this all wrong? I'm looking to get at LEAST 2.3.2, but I noticed musescore 3 came out and I've been wanting to give it a shot.


In reply to by Shoichi

Yes, I have seen that. But when I do rollApp it doesn't allow playback and other things without paying a premium I shouldn't have to pay, especially considering MuseScore is free. So I took the linux route. I went into the terminal and did the following two commands:
sudo apt-get update
sudo apt-get install musescore

From there, it installed MuseScore 2.0.3, which is fairly feature-packed, but it's having trouble with .mscz files from MuseScore 2.3.3. So I'm looking for a .deb file for MuseScore 3 or a way to turn an AppImage into a .deb file, because ChromeOS 71 does not support FUSE, which is needed to run AppImages. If that isn't possible, I'm also looking for a 2.3.3 .deb file so that I can open my projects from my last device (I have the files, they just don't open on 2.0.3).

In reply to by jacobcshort78

Hi, Debian maintainer of MuseScore here.

Try using the .deb files from Debian stable-backports:

(You will need all three, and in this order.)

Perhaps just adding stretch-backports to the sources.list will make them available; otherwise, download the .deb files for the correct architecture (run dpkg --print-architecture to figure out which to use) and install them with sudo dpkg -i, followed by a sudo apt-get -f install at the end to add dependencies.

I’d been trying to figure this out, but the Chromebook Anatoly got me an account on did not have APT installed.

This will give you 2.3.2; 3.0 just came out and is still considered not ready to supercede it yet (furthermore, it fails to build, but a snapshot from 13th December works) and has other issues. It’s available in Debian experimental (the soundfont is shared):

In reply to by mirabilos

So. I revisited this just now with the newfound motivation (for some reason) to have at least 3.1 on here because why not lose all of my progress to a bug?
Anyways, I installed the -common file for 3.1 and it worked out great. However, when I went to install musescore-snapshot, it didn't work. Before, I thought I was using the wrong architecture. I decided to use dpkg to install the file instead and see exactly why it hasn't worked, and it gave me this:

(Reading database ... 44017 files and directories currently installed.)
Preparing to unpack musescore-snapshot_3.1+dfsg1-1_amd64.deb ...
Unpacking musescore-snapshot (3.1+dfsg1-1) over (3.1+dfsg1-1) ...
dpkg: dependency problems prevent configuration of musescore-snapshot:
musescore-snapshot depends on libc6 (>= 2.27); however:
Version of libc6:amd64 on system is 2.24-11+deb9u4.
musescore-snapshot depends on libqt5core5a (>= 5.11.0~rc1); however:
Version of libqt5core5a:amd64 on system is 5.7.1+dfsg-3+deb9u1.
musescore-snapshot depends on libqt5gui5 (>= 5.8.0); however:
Version of libqt5gui5:amd64 on system is 5.7.1+dfsg-3+deb9u1.
musescore-snapshot depends on libqt5qml5 (>= 5.10.0); however:
Version of libqt5qml5:amd64 on system is 5.7.1-2+b2.
musescore-snapshot depends on libqt5widgets5 (>= 5.11.0~rc1); however:
Version of libqt5widgets5:amd64 on system is 5.7.1+dfsg-3+deb9u1.
dpkg: error processing package musescore-snapshot (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Processing triggers for man-db ( ...
Processing triggers for shared-mime-info (1.8-1+deb9u1) ...
Errors were encountered while processing:

So I tried installing the libraries I needed, starting with libc6, but terminal said no, specifically that this would "break locales, and deconfiguration is not permitted". Does that mean that I literally am unable to install the required libraries, or is there a way to enable deconfiguration, or am I just doing this wrong?

On a lighter note, however, MuseScore 2.3.2 is now playing audio on ChromeOS, and it's never done that for me before. I've always exported as an MP3 to hear my creations.

In reply to by jacobcshort78

“Version of libqt5gui5:amd64 on system is 5.7.1+dfsg-3+deb9u1”

This means: “You have stretch (Debian 9, stable, oldstable in another two weeks) but want to install a package for unstable.”

Try the .deb from (I’ll update them as I get to them, ran into bugs and was strongly urged to wait for 3.1.1 before letting it loose onto users, plus real life is busy atm).

If it’s armhf or arm64 instead of amd64, I might be able to do a build on a porterbox if needed…

In reply to by jacobcshort78

Thanks for the confirmation that this works, this is worth immensely much.

The location is temporary. In a month or so, 3.1.1 will be available as package musescore3 in the stretch-backports-sloppy and buster-backports distributions, the timing being most dependent on the various cogs in Debian.

In reply to by mirabilos

Bug report because I'm not sure where to put it:

With or without MDL installed:
-When vertical scrolling with a trackpad, the screen often jerks left and right
-Horizontal scrolling with a trackpad is very broken, always jerky and not always in the intended direction
-Workaround: Hold shift when scrolling to scroll horizontally.
-MIDI keyboard refuses to work at all, even though it works with other programs (though those other programs are not debian...does debian on ChromeOS support MIDI devices?)
-Scores with percussion instruments become very laggy during playback and sounds very glitchy, as if in slow motion, though this only happens when working with a different soundfont, specifically GeneralUserGSv1.471.sf2

With MDL installed:
-Score often doesn't play from selected part, instead playing from where it previously stopped
-Weird format when using "MDL" palette
-MDL crashes during uninstall

There ya go. Musescore is still usable, but these kinda get in the way

In reply to by jacobcshort78

Hi again,

lemme see… scrolling is a UI issue, I don’t know which GUI backend Qt on a Chromebook uses (might be Wayland or X11 or something else entirely), and I don’t think MuseScore is at fault there, this sounds to be more like an input event handling issue. I’m unsure if there’s something you can do inside the Debian environment to help… perhaps ask in some Linux-on-Chromebook user forum?

MIDI is a part of audio, and I know that the Linux environment used to have no access to audio at all, and that that was only recently changed; I imagine they only pass dsp through, not MIDI, now. I’d suggest installing JACK both inside the Debian environment and natively on ChromeOS (if this is at all possible) and connect these two, or, again, ask around, although nobody in those forums might know about this.

Laggy playback… I encounter this in large scores (many instruments) where it’s a CPU issue (check that your CPU utilisation does not stay at 100%, both total and per-core), or with large SF3 soundfonts (which I know need to be uncompressed into RAM), so also check your RAM usage. I don’t know if MuseScore also loads SF2 soundfonts entirely into RAM, but try removing unused soundfonts from the synthesiser settings if your RAM is getting full.

The MDL issues are probably real MuseScore issues. I’ve never used MDL, so I have no idea about them. I’d suggest waiting until an updated package will be out (I’m aiming at dealing with the upcoming (this weekend, perhaps?) 3.2 release soon after it comes out, although RL still might get into the way, still in the midst of moving houses), retry and only then report the issue. There is one parallel to the above, though: MDL comes with a rather large (SFZ) soundfont, so if your RAM is already full from your normal SF2/SF3 soundfont configuration, go figure.

If you don’t need the full instruments from the MuseScore_General HQ soundfont, install… and uninstall the musescore-general-soundfont or musescore-general-soundfont-lossless package afterwards (or use the Debian alternatives system to handle which one is used).

I hope this helps you further.

To be clear: I don't have any experiences with Chromebook or deb packages ;-). But some thoughts:

I don't think, a deb for 3.0 file is available yet, but I suppose will be available in future.

As mentioned on the download page (, you'll find also deb packages on unstable (sid) site: But as mentioned, not sure if it works with ChromeOS.

On the other hand, I thought, if you install Linux via Crouton it should be also possible to get run the AppImage?

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