Appimage and flatpak version crashing.
Recently Musescore started crashing badly.
It opens with startup screens, questions about sending telemetry fine. But then it starts with a standard "select from" form that shows some scores. If you try to cllick one or just close that screem bth the appimage and flatpak version crash abruptly and badly affecting the whole system.
I tried starting it with the -w and -F options. That did not help.
I finally tried it with full_commandline.appimagename and it opened without problems. I then changed the startup preferences to start with the most recent file. I could close and restart.
The original attempt to start tried to open some file ":/data/*mscz" and I think the : is what cause the crashing.
No I will need to figure out how to change the startup for the flatpak. If I can change that config I can start the flatpak version too.
Can someone verify that if you start with an existing musescore file as a parameter the application starts fine, and if you then change the default file to open you can just keep starting and working?
If this gets verified can a bug-report be started somewhere?
Comments
I tried with the most recent appimage and flatpak versions.
that ":" refers to files built into MuseScore, in some sort of virtual and read-only filesystem
thanks for your reply. I only know for certain that explicitly stating an exisiting filename as a parameter will start correctly with that file open.
In flatpak I have tried deleting the ini file, musescore createed an empty new one but still crashed with the window where it offers to select score.
I then tried setting the "replayscore" to False. Still crashed. Because it still asks for a file to open in the pop-up.
In reply to thanks for your reply. I… by J Muller
No idea what "replayscore" might be?
In reply to No idea what "replayscore"… by Jojo-Schmitz
It is in the UI section of the ini file. I guess it means re-playing the score on startup.
Since the appimage version no longer crashes I am looking to see if the option that starts the "open" popup at the start can be disabled. Then, ate least, I can use both to edit scores.
Since the flatpak version can run when logged in as guest that could be a good idea for a lab.
In reply to It is in the UI section of… by J Muller
There's no such thing, not in the ini files I see. Do you mean
playback\playRepeats
?In reply to It is in the UI section of… by J Muller
The setting to disable that first "open popup" as you call it is to be found in
Edit → Preferences
and is calledStart Center
In reply to The setting to disable that… by jeetee
Since musescore crashes when you try to do anything with the "start-centre" there is no way to get to the "edit"/"preferences".
The idea is to find the setting in the ini-file that affects the "start centre" and manipulate that, then start musescore without the "start centre" showing.
On the appimage version one can simply bypass the "start centre" by supplying a path to a working mscz file. Then I could change the preferences.
That should work on flatpaks as well. Start the flatpak from a comand-line and supply the full path to a working mscz file. When that opens without the "start centre" activating & then change the setting.
I use the flatpak in cloudready and cannot use the command-line to start the flatpak, so I cannot disable the "start centre". Hoping for an answer.
In reply to Since musescore crashes when… by J Muller
Use the -w commandline option.
In reply to Use the -w commandline… by Jojo-Schmitz
I can do that in appimages, where it did not work.
I cannot do that in flatpaks because I cannot use the commandline. I can only start them by clicking on an icon.
In reply to Since musescore crashes when… by J Muller
just a quick browse through the preferences file (which is human readable) shows this setting:
application\startup\showStartCenter=false
in the
[ui]
section.I presume that at first start it is still missing or set to true. So if it exists, write it to false; if not, then add it as above.
In reply to just a quick browse through… by jeetee
That worked. I can now start the flatpak. But the "open" dialogue to open a file will not work.
I bet there is something wrong with the implementation at communicating with the OS on the musescore side.
In reply to That worked. I can now start… by J Muller
People who can start the appimage or flatpak versions can simply start with the name of a file specififed in the command line. That can be edited or changed.
But one cannot open another file because the dialogues with the OS do not work.
In reply to That worked. I can now start… by J Muller
If it works in the AppImage, then it works on the MuseScore side. flatpak is not created, nor supported by MuseScore itself; it is maintained by a community effort. If they mess up OS integration, then they are the ones that need to fix it.
There is a setting choosing whether to use the native file dialogs or not. Go to preferences → advanced settings to toggle it.
I'm not sure if this relates to the same problem: https://musescore.org/en/node/303598
But if so, I'm new to Linux and am very curious if there is a (partial) solution. And if so, I would be grateful if it could be explained step by step in layman's terms :)
I upgraded debian 9 to debian 10 and it all works fine now.