Issues with AppImage File
I don't know if it's an issue with the most recent form of Linux on the Chromebooks but for some reason every time I try to get the newest version of Muse-score to work I keep getting this error message
fuse: device not found, try 'modprobe fuse' first
Cannot mount AppImage, please check your FUSE setup.
I have the latest version of Fuse, I've been trying to troubleshoot around this but I need help. Has anyone else had this issue, do you plan on making a video? Or could you send me one I have an Acer Chromebook Spin 11
Comments
I've never heard of Fuse, and have never seen any error message involving it when running MuseScore on my Chromebook. Can you explain more about it and your use or it and how it relates to MuseScore?
In reply to I've never heard of Fuse,… by Marc Sabatella
I think it might've been an issue of having to restart the computer to get it to run but now when I open it up it crashes the computer and makes it reboot all over again
In reply to I think it might've been an… by octaviawillia
Now that is an unfortunate known (to me, and a few others) issue with the latest version of ChromeOS, They have broken Linux apps pretty badly. It's been reported to Google, but so far no word on a fix. For me, MuseScore doesn't crash the system on open, but it like other Linux apps does crash the system a lot. It seems to help in some ways to disable GPU support in chrome://flags (search for "GPU" for crostini-gpu-support).
In reply to Now that is an unfortunate… by Marc Sabatella
Thanks I'll try that for now.
Same thing happens on normal Linux, too:
In reply to Same thing happens on normal… by mirabilos
Fixed by manually installing the
fuse
package, which is not installed by default:So this isn’t quite a “no root, no installation needed” solution… especially as it involves a kernel module…
In reply to Fixed by manually installing… by mirabilos
I had given up on this when I wrote to the forum in March of this year and could not get a solution, having missed the info you posted here the year before! Finally I can run musescore not billed as [and hopefully not behaving as] "unstable." The line you posted above saved me!