Autosave disappear when closing

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1. Save a file
2. modify somethin, add mesures, etc.
3. wait for the autosave to be created.
4. Make MS crash the way you want (just killing it should works)
5. Open the autosave version, you have the most recent version
6. Close it. It ask if you want to save change. As you are unsure at this point if you want to override the last saved with the autosave, you usually answer « do not save ».
7. The autosave file disappeared completely. It is not even in the dustbin.

This is an UI problem. A « do not save » button is not supposed to have any action on what is written on the disk and is usually a safe command if you don’t care about what is loaded in ram. It would be more clear if you make distinct and more explicit buttons. I suggest something like :

• Override main file
• Delete autosave file
• Close without saving
• Discard

Supporting files, videos and screenshots

Not needed

In which versions of MuseScore Studio is this issue present?

4.6.3 flatpak

Regression

Choose option...

Operating system

Manjaro

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

No files or tests are named. First reproduce the autosave workflow in MuseScore Studio 4.6.3 on the reported flatpak setup, then trace the close/discard path for autosave files. Done means the close choice clearly distinguishes discarding loaded changes from deleting the autosave, with the reported file-preservation behavior verified.