Problems running MuseScore 2.0 on Fedora 23
I've just upgraded my Linux installation to Fedora 23. I then installed the current version of MuseScore from the Fedora 23 repository, using the YumEx tool as directed on the musescore.org downloads page. This is version 2.0.1 (2.0.2 is not yet available for Fedora).
Anyway, whenever I try to start MuseScore, either from the program icon or by opening a MuseScore file, I get a flurry of activity indicating Fedora is trying to load the program and then nothing. It fails to run at all.
Has anyone managed to get MuseScore to work with Fedora 23? if so, how?
Comments
If you run it from the command line, any interesting console output? Maybe try using the "-F" option to revert to factory settings, or try "-w", or "-s", or other options that seem possibly relevant as documented in the Handbook under "Command line options".
In reply to If you run it from the by Marc Sabatella
Nothing with most options but debug mode spits out some information and then crashes out sending a report automatically (probably somewhere in the system now).
This is what I get:
# mscore -d
QIODevice::read (QFile, "/usr/share/fonts/bravura/glyphnames.json"): device not open
QIODevice::read (QFile, "/usr/share/fonts/bravura/metadata.json"): device not open
Segmentation fault (core dumped)
I'm guessing there's a problem with musefonts access that prevents further loading of the program.
In reply to Nothing with most options but by Ayesongs
In fact, those font directories don't exist. Some bug in installing musefonts?
In reply to In fact, those font by Ayesongs
I don't think they are supposed to exist, these files are (or rather should be) built into MuseScore
In reply to In fact, those font by Ayesongs
OK - I set up some symbolic links to the missing font directories (they were in a subdirectory for musescore) and cured the font file problem. However musescore still crashes out with just the segmentation fault to report. Any ideas, folks?
In reply to OK - I set up some symbolic by Ayesongs
Can you post more of the console log? Or are you saying there is nothing?
That's all I've got. The full output in debug mode (-d)
In reply to That's all I've got. The full by Ayesongs
If you have Qt 5.5 installed, I think you need to convince MuseScore to use 5.4 instead. Not sure if that's the problem here, but it is probably something else you would need to address even if it isn't the cause of the crash.
I just tried MuseScore in Fedora 23 Beta, running in a VirtualBox on Windows 7. I installed MuseScore from the Fedora repo. If I try to start mscore (from the commandline) it crashes with a segfault and doesn't start. I will do more testing after Fedora 23 is released (november) and I will do a real Fedora 23 install on my Linux computer. I want to try if it makes any difference if I compile from sources myself. Anyway, it seems the Fedora packager(s) and/or the MuseScore developers have still some work to do for MuseScore 2.x +Fedora 23.
BTW: I am using MuseScore on Fedora 22 with Qt 5.5. And it doesn't crash like this.
The issue has already been reported in Fedora Bugzilla. Hope it will be fixed soon :-(
https://bugzilla.redhat.com/show_bug.cgi?id=1262528
I tried the official Fedora 23 package for Musescore on a virtual machine (segfault, crash)
I also tried to compile from GIT development sources myself on another Fedora 23 system: It works nicely.
So it looks to me something is wrong with the Fedora 23 RPM build and/or packaging.
It seems the cause has been found. You will also find a workaround there now. So a fixed package can't be far away :-)
//bugzilla.redhat.com/show_bug.cgi?id=1262528
In reply to It seems the cause has been by mtarenskeen
This looks hopeful. I'll give it a go.
Unfortunately Fedora does still not offer Musescore 2.0.2.
In reply to Unfortunately Fedora does by musescore38
Please report this downstream to fedora/redhat people https://bugzilla.redhat.com/show_bug.cgi?id=1246733
Already done. Regards.