musescore / musescore/MuseScore
Fedora build of 4.6.3 unable to load MuseSounds
@konradglas is already working on this.
Since Oct 28, 2025.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Description with steps to reproduce
Greetings. I maintain the Fedora musescore package. Fedora 43, to be released next week, will make 4.6.x versions available to our users. However, an early tester reports that MuseSounds does not work:
https://bugzilla.redhat.com/show_bug.cgi?id=2404987
I can reproduce this with a build of 4.6.3 for Fedora 42. Control reaches muse::musesampler::MuseSamplerLibHandler::init() and passes the first test (that initLib is non-NULL). Then initLib() is called and does not return ms_Result_OK, so logs the Could not init lib message and returns false. I can't debug this issue, because libMuseSamplerCoreLib.so has a missing symbol, DRM::AntiDebug::scheduleThreadTimedCrash. Since you have deliberately prevented me from debugging the issue, would you please debug it for me?
Supporting files, videos and screenshots
15:52:17.311 | ERROR | main_thread | MuseSamplerLibHandler::init | Could not init lib
15:52:17.311 | ERROR | main_thread | MuseSamplerResolver::init | Could not init MuseSampler: /home/jamesjer/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so, version: 0.102.2
In which versions of MuseScore Studio is this issue present?
4.6.0 - 4.6.3
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Fedora 42, 43, and Rawhide
Additional context
Fedora 41 and 42 don't provide MuseScore versions later than 4.3.2, because Qt issues made 4.4.x and 4.5.x unusable. To reproduce, you will probably have to acquire a Fedora 43 installation, or else do you own Fedora 41 or 42 build of a source RPM like I did.
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.