Musescore 4 crashes whenever I try to save a file

• Jan 17, 2024 - 04:05

Whenever I try to save a score as a midi, or anything else, musescore (4 but I also had this problem when I started out with 3 before updating). My scores will only save if I save to the cloud and nothing else. I lost hours of work to this bug and would really appreciate any help!


Comments

In reply to by bobjp

Before updating from Musescore 3 to 4. I meant to say exporting to Midi. Right when I press export to midi it opens up my files but it crashes before I can select a location. Don't know if its a permissions thing but would you happen to know where I can edit those just in case?

In reply to by Another3Person

Running musescore 4.4.4. Load a midi file. Press save button. Running on linux from command line I get the following error messages in the console.

13:51:14.633 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: file-save
13:51:14.636 | WARN | main_thread | Qt | qrc:/qml/MuseScore/Project/AskSaveLocationTypeDialog.qml: Setting initial properties failed: AskSaveLocationTypeDialog does not have a property called sync
13:51:16.333 | WARN | main_thread | Qt | qrc:/qml/Muse/Ui/internal/FileDialog.qml: Setting initial properties failed: FileDialog does not have a property called selectExisting
13:51:16.367 | ERROR | main_thread | crashCallback | Oops! Application crashed with signal: [11] SIGSEGV-Invalid memory reference

In reply to by bobjp

I downloaded stone2test.mscz. I opened it in musescore, and saved without any problem. But, it didn't offer me the choice of cloud / local machine, it just saved it to my local machine.

The file I had problems with was a midi file, this links to directly to the midi file: https://imslp.org/wiki/Special:ImagefromIndex/151200

I can upload the actual .mid file directly to this post, if needed, but it seems more courteous to IMSLP to link to their site.

With this midi file, I open it in musescore, and it plays, and I can edit it, but if I say save as, or save, or save copy, it offers the choice of cloud or PC, and when I select PC, it crashes.

When I restart, musecore offers to restore the "unexpectedly quit" session. If I say yes, it cannot find the file: /home/myLinuxUser/.local/share/MuseScore/MuseScore4/new_project.mscz

The directory exists, the file doesn't. Musescore can export a file to this directory, so has write permissions.

Note: musescore allows me to export the midi as an mxl file, but if I load the exported mxl, it has the same symptom if I try to save it - ie it offers to save to cloud or PC, and it crashes when I select PC.

In reply to by oflarst

Tle lack of a Git-SHA at the end of the version string is a tell-tale sign that you're not using the AppImage. And only that is supported here, so go any report this issue to Gentoo or FlatPak or whatever, esp. FlatPak is known to have serious issues, or switch to the AppImage from the download page is this site here

In reply to by Jojo-Schmitz

For other people having the same symptom as I do, and landed here, I downloaded the AppImage from the Musescore github site https://github.com/musescore/MuseScore/releases

chmod +x MuseScore-Studio-4.4.4.243461245-x86_64.AppImage
./MuseScore-Studio-4.4.4.243461245-x86_64.AppImage

load the midi file, save doesn't crash, and will create an mscz file.

You can now run your locally built version, the mscz file can be loaded, edited and saved.

If I find the cause of the bug in the gentoo build, I will post here again.

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