Hi Jojo! I'll follow up on this as I'm having the same issue. I'm running Fedora 33 with musescore version 3.5.2 Revision 3543170. F9 or selecting palette from view produces a blank palette folder.
actually it doesn't on relate to windows 10 I guess. I figure it's a mscore issue overall as it appears quite heavily in the search.... so should I open a new case?
I've actually never used an appimage, however I just did and voila! It works just fine from a Gnome environment.... so indeed, back to the Fedora people, however it just seems easier to use the appimage at this point. I do run different window managers and found that in MATE, the appimage did not work but that is a non-issue for me. Thanks and sorry to bother this windows 10 "issue"... lol
It's semi-common on Linux systems when not using the AppImage, because often the version provided by the distribution maintainers are not built correctly - which is one of the reasons we provide the AppImage :-). I hadn't heard reports of issues with AppImage on MATE though. WHat exactly goes wrong? If it seems likely to be a general problem on that system, we should have a separate issue for that.
Thanks Mark
I discovered the empty palettes issue and it has to do with the Fedora 33's default Gnome environment, Wayland interpreter and Nvidia. Hard to pinpoint at first as I have a laptop running an nvidia chip and also have the thunderbolt port out to a separate monitor. Depending on which screen I opened musescore in , the problem would appear or not... odd. When the palette was empty it throws lots of wayland and egl errors. The docking buttons on the palette also never work properly as the palette disappears instead of docking as it should.
The MATE issue was a one time thing hanging for the pop-up screen for the chrome reporting dialog that comes when you first run the appimage. Once I ran the appimage on the gnome environment it was fine on MATE after that.
Ah yes, a number of systems have an issue displaying the startup dialog (asking for permission to send telemetry data).
Regarding the palette issue, as I recall it has to do with Open GL drivers and/or supporting libraries used by the QML subsystem we rely on for palettes. Depending on how the package is built and configured, you can end up with missing or wrong versions.
Comments
What? More details please...
What version exactly?
In reply to What? More details please… by Jojo-Schmitz
Hi Jojo! I'll follow up on this as I'm having the same issue. I'm running Fedora 33 with musescore version 3.5.2 Revision 3543170. F9 or selecting palette from view produces a blank palette folder.
These are the mscore packages I have installed.
[mark@localhost ~]$ rpm -qa | grep mscore
mscore-fonts-all-3.5.2-4.fc33.noarch
mscore-3.5.2-4.fc33.x86_64
mscore-doc-3.5.2-4.fc33.noarch
mscore-musejazz-fonts-3.5.2-4.fc33.noarch
mscore-mscoretext-fonts-3.5.2-4.fc33.noarch
mscore-mscoretab-fonts-3.5.2-4.fc33.noarch
mscore-gootville-fonts-3.5.2-4.fc33.noarch
mscore-fonts-3.5.2-4.fc33.noarch
mscore-bc-fonts-3.5.2-4.fc33.noarch
Thanks
Same issue with the AppImage? If that work, complain to the Fedora maintainer
And how would that relate to the OP's problem on Windows 10?
In reply to And how would that relate to… by Jojo-Schmitz
actually it doesn't on relate to windows 10 I guess. I figure it's a mscore issue overall as it appears quite heavily in the search.... so should I open a new case?
In reply to actually it doesn't on … by ripsix
I've actually never used an appimage, however I just did and voila! It works just fine from a Gnome environment.... so indeed, back to the Fedora people, however it just seems easier to use the appimage at this point. I do run different window managers and found that in MATE, the appimage did not work but that is a non-issue for me. Thanks and sorry to bother this windows 10 "issue"... lol
It's semi-common on Linux systems when not using the AppImage, because often the version provided by the distribution maintainers are not built correctly - which is one of the reasons we provide the AppImage :-). I hadn't heard reports of issues with AppImage on MATE though. WHat exactly goes wrong? If it seems likely to be a general problem on that system, we should have a separate issue for that.
In reply to It's semi-common on Linux… by Marc Sabatella
Thanks Mark
I discovered the empty palettes issue and it has to do with the Fedora 33's default Gnome environment, Wayland interpreter and Nvidia. Hard to pinpoint at first as I have a laptop running an nvidia chip and also have the thunderbolt port out to a separate monitor. Depending on which screen I opened musescore in , the problem would appear or not... odd. When the palette was empty it throws lots of wayland and egl errors. The docking buttons on the palette also never work properly as the palette disappears instead of docking as it should.
The MATE issue was a one time thing hanging for the pop-up screen for the chrome reporting dialog that comes when you first run the appimage. Once I ran the appimage on the gnome environment it was fine on MATE after that.
Ah yes, a number of systems have an issue displaying the startup dialog (asking for permission to send telemetry data).
Regarding the palette issue, as I recall it has to do with Open GL drivers and/or supporting libraries used by the QML subsystem we rely on for palettes. Depending on how the package is built and configured, you can end up with missing or wrong versions.