Description of problem: Mageia 7 is shipped with MuseScore 3.0.5. There have been 4 other releases until today (July 2nd), with many bugfixes. Could you please consider providing the latest version of MuseScore? Version-Release number of selected component (if applicable): $ rpm -qa | grep mscore mscore-fonts-3.0.5-2.mga7 mscore-3.0.5-2.mga7
(In reply to Sébastien Morin from comment #0) > Description of problem: > > Mageia 7 is shipped with MuseScore 3.0.5. > There have been 4 other releases until today (July 2nd), with many bugfixes. > Could you please consider providing the latest version of MuseScore? > It should at least be possible to do this for cauldron. I don't know whether pushing it to Mageia 7 is allowed https://wiki.mageia.org/en/Updates_policy#Version_Policy Assigning to the registered maintainer.
Version: 7 => CauldronWhiteboard: (none) => MGA7TOOAssignee: bugsquad => rverscheldeCC: (none) => marja11
Summary: Please upgrade MuseScore 3.0.5 to the current version (3.2.2) => Please upgrade MuseScore current version (3.3.0)
Component: RPM Packages => BackportsVersion: Cauldron => 7
The RPM available for Mga7 in backports_testing is working, but it seems there is a bug in that version: when creating a new music score, the second screen (choose the instruments) leads to an empty box. It works fine if you choose a standard orchestral type (symphony orchestra, jazz band, quartets and so…), but you can't choose the instruments individually at this stage.
(In reply to Sébastien Morin from comment #2) > there is a bug in that version: when creating a new music score, the second > screen (choose the instruments) leads to an empty box. This is fixed in revision 1.1
MuseScore 3.0.5 has bugs ... I need MuseScore 3.3.4 to be able to create scores with tablatures for my diatonic accordion ! Please upgrade the version of MuseScore available.
CC: (none) => pithomas
Release 3.3.4 available in Core/Backports_testing repo!
CC: (none) => geiger.david68210
By that way, I just found 3.3.0 version, not 3.3.4 version. But it seems OK for what I need. I thank you.
I have installed version 3.3.4 from Backports_testing but when I run Musescore, the About info is still “3.3.0”, so I am not really sure what version I am testing!
Here is what I get when I run mscore from a konsole: $ rpm -qa | grep mscore mscore-3.3.4-1.mga7 mscore-fonts-3.3.4-1.mga7 $ mscore qrc:/qml/palettes/PaletteTree.qml:149: Error: Cannot assign to non-existent property "color" Soundfont '"MS_General v0.1"' is not MuseScore General, cannot update expressive Soundfont '"MS_General v0.1"' is not MuseScore General, cannot update expressive Soundfont '"MS_General v0.1"' is not MuseScore General, cannot update expressive Soundfont '"MS_General v0.1"' is not MuseScore General, cannot update expressive ScoreFont::draw: invalid sym 0 acceptNavigationRequest( QUrl("https://connect2.musescore.com/?version=3.3.0.") , QWebEnginePage::NavigationTypeTyped , true ) [1:17:1224/121830.680993:ERROR:adm_helpers.cc(73)] Failed to query stereo recording. libpng error: Read Error <My_First_Score> QMutex: destroying locked mutex QObject::disconnect: No such slot Ms::MyWebView::stopBusy(bool)
I am no longer able to find MuseScore 3.3 from Mageia CCM. I solved my problem by using MuseScore-3.3.4-x86_64.AppImage
Testing the RPM available in Core Backports Testing: $ rpm -qa | grep mscore mscore-fonts-3.3.4-1.1.mga7 mscore-3.3.4-1.1.mga7 When opening Musescore, this error message pops up: Impossible de lire le fichier /usr/share/mscore-3.0/demos/My_First_Score.mscx : No such file or directory (Impossible to read file /usl/share/… etc.) Musescore seems to work despite this error message.
Hmmm, not working so well: we're back to the problem I mentionned in comment #2 : the list of instruments is empty when you try to choose them individually.
Even the AppImage is “not working” (cf comment #2) anymore once the 3.3.4 RPM is installed. It needs to be fully uninstalled, and then install 3.0.5 again so that you can use the AppImage again… mscore-3.3.4-1.1.mga7 needs to be repackaged ;)
The empty list of instruments comes from an error in the location of the file intruments.xml: in Edit → Preferences → Score tab, it is /usr/share/mscore-3.0/instruments/instruments.xml, it must be /usr/share/mscore-3.3/instruments/instruments.xml. But as said in https://musescore.org/en/comment/972504#comment-972504, it would better to have /usr/share/mscore-3/instruments/instruments.xml defined in the Mageia RPM. Pierre
Summary: Please upgrade MuseScore current version (3.3.0) => Please upgrade MuseScore current version (3.4.1)
Hello! I have tested mscore-3.4.1 which is in Mga7's Core/Backports_testing at the moment and this version worked perfectly well on my system. All of the problems that I described in previous comments have been solved. This package is ready for further testing by the QA team ;)
The package mscore 3.3.0, release 1.1mga7, architecture x86_64 failed to install. Would it be possible to provide the package for MuseScore 3.4.2, released on February 7, 2020? The last version of MuseScore provided and installed on my computer is 3.0.5 !!!
CC: (none) => pavelfric
mscore 3.4.1 is in Core/Backports_testing repo!
Now I can see it. The update of repos helped.
Bonjour, Everything is updated and OK for me with MuseScore-3.4.2-x86_64.AppImage. Pierre
Source RPM: mscore-3.0.5-2.mga7 => mscore-3.4.2-2.mga8Summary: Please upgrade MuseScore current version (3.4.1) => Please upgrade MuseScore the current version (3.5.0)Component: Backports => Release (media or process)CC: (none) => sysadmin-bugsVersion: 7 => Cauldron
Thanks reporting this, mscore-3.5.0-1.mga8 is already in Cauldron folks. At this time, I see mscore-3.4.1-1.mga7.x86_64.rpm in Mageia 7, x86_64 media, core-backports_testing.
Component: Release (media or process) => RPM PackagesCC: sysadmin-bugs => (none)
(In reply to Aurelien Oudelet from comment #19) > Thanks reporting this, > > mscore-3.5.0-1.mga8 is already in Cauldron folks. > > At this time, I see mscore-3.4.1-1.mga7.x86_64.rpm in Mageia 7, x86_64 > media, core-backports_testing.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
After upgrading from Mageia7 to Mageia8 on my main computer, the bug I mentioned in comment #2 was back again. It is necessary to change the path as suggested in comment #10 and indicate: /usr/share/mscore-3.5/instruments/instruments.xml
Resolution: FIXED => (none)Status: RESOLVED => REOPENED