File Save dialogue soon ceases to appear (Musescore ver 3.6.2 on Linux Ubuntu 18.04.5)
Musescore ver 3.6.2 on Linux Ubuntu 18.04.5
The File Save dialogue just after startup appears normally, but after a few minutes of use it won't be visible any more, the Musescore window does fade to darker colors but the File Save dialogue isn't visible anywhere.
(ctrl-s works just fine if it's not a new score still needing to be assigned a file name.)
I tried switching windows, moving windows, switching desktops, nothing revealed the File Save dialogue.
The issue has always appeared so far using 3.6.2, although I haven't been able to spot after WHICH steps it appears, maybe after using some specific tool, e.g. after assigning an articulation, I don't know yet but it ALWAYS occurred so far ("so far" = a couple of easy scores for school pupils, 4 trumpets and 2 or 3 saxophones).
Hence, the following actions become impossible via the Musescore GUI and require using the operative system:
- saving a copy with another name
- saving with another name and continuing with it
(Obvious) workarounds for the above actions, provided you did save immediately after creating a new score (the File Save dialogue works just fine after launching Musescore and creating a new score):
- ctrl-s, switch to a terminal or Nautilus window (Nautilus is the GUI file manager) and make a copy of the file with another name, switch back to Musescore
- exit Musescore, rename the file, restart Musescore and load the file with its new name
IN CASE THE WORK HASN'T BEEN SAVED BEFORE, NOT EVEN ONCE, A WORKAROUND WHICH HAS JUST WORKED HERE IS:
in the terminal window, I issued this command:
kill -9 `pgrep mscore`
I restarted Musescore, I chose to restore the previous session, I got the score I was working on, ctrl-s and I've been asked a file name and the file has been saved.
The problem also appears when exporting.
Workaround: exit, restart Musescore, export.
EDIT: on this score, it did not happen afterwards, first time without that problem (in... maybe 10-15 hours in different sessions).
Was it because it was restored from a killed session?
Was it because I reported the problem (LOL)?
I'll post further details if I ever come to narrow it down (actually I hadn't posted before because I was hoping to get to a tighter focus).