Downloading MuseScore_General_HQ extension fails
Reported version
3.5
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
bij het bijwerken van de databronnen krijg ik steeds hetzelfde resultaat zoals te zien in de bijlage
| Attachment | Size |
|---|---|
| Schermafbeelding 2020-12-30 184344.png | 39.63 KB |
Comments
See https://musescore.org/en/node/312255 and https://musescore.org/en/node/312007 for a workaround:
try http://extensions.musescore.org/3.5/extensions/MUSFE.muxt and run MuseScore on the command line "mscore -E mdl.muxt" or open MuseScore and drag and drop the muxt file into it.
Similar issue exist for the other extension, MDL, see #299263: MuseScore with MDL installed hangs
Found to be present on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34 also.
Tried the workaround? Now http://extensions.musescore.org/3.6/extensions/MUSFE.muxt
Yes. It works.
(oops, posted on, wrong issue by mistake; reopened)
It probably is the same underlyig cause as for MDL, but suffiently different to be kept open for the time being. Better than a circular duplicate ;-)
Agreed. Also my mistake (which I corrected) caused a circular duplicate. Seems this is possible in our issue tracker since it does not have field for which a duplicate issue is considered the duplicate of.
See https://github.com/musescore/MuseScore/pull/7533
Fixed in branch 3.x, commit 608827b91a
fix #314950: fix inability to download extensions
Automatically closed -- issue fixed for 2 weeks with no activity.
Just installed version MuseScore-3.6.2.548021803-x86_64 and when trying to download the extension "MuseScore General..." the download process fails at random percentages, my internet seems to be operating optimally. The same happens to the "MusecoreD Dumli..." (the columns can't be resized to read the full name).
Errors:
"Unable to download, save and verify the package. Check your internet connection".
"Failed, try again"
The issue has been fixed in the 3.x branch, so would be in 3.6.3 if there ever is such a thing (as per the Powers To Be there won't be a 3.6.3 though), else in 4.0.
Until then the workaround still applies
Actually it may not be in 4.0, as that PR has not been ported to that...