3.5.1 Download page actually offer 3.5.2

• Nov 29, 2020 - 21:56

I tried to download the previous version 3.5.1.
From the Home page, I click on "Musescore 3.5.1 Release":

From here, AppImage and Windows links actually download 3.5.2 release.


All these pages always redirect to thw latest version. Previous versions are available elsewhere. And esp 3.5.1 should not get used at all, it can cause serious corruptions

Indeed, there should be no reason to want 3.5.1. I guess you are trying to workaround the crash involving text within horizontal frames within vertical frames, but I am pretty sure that crash would also be in 3.5.1. It might not be in 3.5, but that's definitetly not something you want unless you wish far worse problems. Instead, you'd need to back up to 3.4.2 to have a stable release that avoid the bug in question - but unfortunately, that will crash on other operations involving horizontal frames within vertical frames (e.g., after deleting one), so I wouldn't really recommend that either.

We're working on figuring out how to fix the crash for 3.6, but meanwhile, I think the better solution for now is to simply replace those unnecessary horizontal frames with plain text.

In reply to by Marc Sabatella

I tried to download 3.5.1 while documenting the issue on the horizontal frames: the idea was to check if that issue were in 3.5.1 also, and give more info. I did not have a backup of version 3.5.1 appimage, and I followed the link in the home page of Musescore (Latest news | MuseScore 3.5.1 Release)...

I just noticed that in that page (https://musescore.org/en/3.5.1), even if the title is "Download MuseScore 3.5.1 Release", you get the last release, so the real comment here was that there is this little inconsistency in the page...
But I can understand that you always point to the last release...

Your hint for text columns is very helpful and I really do not need to switch back for that reason (I agree it is not a good choice keep working with old versions).
Thank you again and kind regards,

In reply to by pbalducci

Thanks for the followup, and I agree, if you do manage to install 3.5.1, it would be good to verify if the problem can be reproduced there. I kind of assume so because the change I made to the code that seems involved was part of that release. If you can't reproduce on 3.5.1, I guess that means I'm off the hook, but I don't think that will turn out to be the case.

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