Bug 2404987 - MuseSamplerLibHandler Could not init
Summary: MuseSamplerLibHandler Could not init
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: musescore
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-19 09:06 UTC by cornosier
Modified: 2026-11-21 02:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-11-10 18:50:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github musescore MuseScore issues 30731 0 None open Fedora build of 4.6.3 unable to load MuseSounds 2025-10-24 22:22:06 UTC

Description cornosier 2025-10-19 09:06:35 UTC
MuseSampler is not recognized by Fedora rpm
It recognizes the Musescore appimage file:

----------------------------------
$ mscore
[...]
[1;31m09:46:55.288 | ERROR | main_thread     | MuseSamplerLibHandler::init | Could not init lib[0m
[1;31m09:46:55.288 | ERROR | main_thread     | MuseSamplerResolver::init | Could not init MuseSampler: /home/gland/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so, version: 0.102.2[0m
-----------------------------------

-----------------------------------
$ MuseScore-Studio-4.6.2.252830930-x86_64.appimage
[...]
[1;32m11:25:09.055 | INFO  | main_thread     | MuseSamplerResolver::init | MuseSampler successfully inited: /home/gland/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so, version: 0.102.2[0m


Reproducible: Always

Actual Results:
You cannot use your MuseSampler bank.

Comment 1 Jerry James 2025-10-20 17:59:28 UTC
Which version of musescore do you have installed?

rpm -q musescore

Comment 2 cornosier 2025-10-20 18:05:32 UTC
Sorry, I should have specified that: 4.6.2, as for the appimage.

# rpm -q musescore
musescore-4.6.2-27.fc43.x86_64

Thank you

Comment 3 Jerry James 2025-10-20 22:59:33 UTC
No problem.  I figured that was what you probably had, but thought I should check.

This is really disappointing.  I have been eagerly awaiting the 4.6 series to get the Qt fixes we need to finally move beyond 4.3.2.  I didn't think to check that Muse Sounds worked.  And I'm really sorry to tell you this, but I am at a conference all this week.  I'm probably not going to have time to debug this issue until next week.  I'll try to find some time during an evening, but I can't promise anything.

Comment 4 cornosier 2025-10-21 05:02:56 UTC
Thank you very much. I'm using the appimage in the meantime.

Comment 5 Jerry James 2025-10-24 22:22:07 UTC
This does not seem to be an issue I can debug, since it involves code inside the MuseSampler library.  I have opened an upstream issue to ask them to investigate.

Comment 6 cornosier 2025-10-25 04:10:34 UTC
Thank you, we'll wait for their response.

Comment 7 Jerry James 2025-11-13 03:53:18 UTC
Sorry for taking so long.  For me, the fix was to do a factory reset.  MuseSampler must be confused by something in the config files written by a previous version of MuseScore.  Start MuseScore, then select the Help menu.  The last item on that menu is "Revert to factory settings".  This will erase any customizations you have made and erase your list of recent scores, unfortunately.  But it does make MuseSampler work again.

Also, if anyone is interested, version 4.6.3 is now in testing: https://bodhi.fedoraproject.org/updates/FEDORA-2025-995baf50af.  This build also enables VST support.

Comment 8 cornosier 2025-11-13 10:54:51 UTC
Thank you very much, it works. Sorry, I didn't think to restore the original configuration, which would have saved you some work.
I downloaded version 4.6.3 and everything is working fine for now.
Thanks again.
Gérard

Comment 9 Lorenzo Miniero 2026-04-07 17:58:44 UTC
Apologies for bumping this issue, but I've only now decided to try and give MuseScore a chance on my Fedora 43 (so far, for various reasons, I was sticking to MuseScore 3 with old rpms). I'm getting the "Could not init" error too, but unlike you, reverting to factory settings didn't fix it for me. This is using MuseScore 4.6.5 from the Fedora repos, and the latest Muse Sounds Manager rpm (2.1.1.912) from MuseScore's downloads.

Comment 10 Jerry James 2026-05-26 21:43:42 UTC
Well ... doggone.  I'm seeing it again now, too.  The problem is that Muse Sounds Manager is a black box.  I can't debug what happens inside it.  If its init function decides to return an error, I have no way of telling what it thinks is wrong.

I'll try a few things and see if I can figure out how to make it happy again.

Comment 11 Aoife Moloney 2026-11-10 17:57:13 UTC
This message is a reminder that Fedora Linux 43 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 43 on 2026-12-02.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '43'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 43 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Jerry James 2026-11-10 18:50:13 UTC
I'm going to close this bug. The MuseSampler library is closed source and has antidebugging features. As in, if I run musescore under a debugger, the MuseSampler library detects the debugger and makes the entire process exit. Upstream has gone out of their way to prevent me from even figuring out what the problem is. If anyone is still seeing this issue, please open an issue upstream: https://github.com/musescore/MuseScore/issues. There is nothing I can do about it unless upstream tells me why the init function returns an error.

Comment 13 Jerry James 2026-11-20 03:42:29 UTC
If anyone is still reading this closed bug, somebody figured it out: https://github.com/NixOS/nixpkgs/issues/318210#issuecomment-2351919536

The bottom line: if you launch musescore from the desktop, MuseSampler works. If you launch musescore from the command line by running /usr/bin/mscore, MuseSampler works.  If you launch musescore from the command line by running plain mscore, MuseSampler does not work.

Those wanting to launch from the command line should probably add this to your aliases:

alias mscore='/usr/bin/mscore'

Comment 14 Jerry James 2026-11-20 13:59:57 UTC
I am going to reopen this bug, because I think there is a simple workaround to this behavior. I'll try a new build with an experimental patch.

Comment 15 Fedora Update System 2026-11-20 22:09:08 UTC
FEDORA-2026-47878747a8 (musescore-4.7.7-2.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-47878747a8

Comment 16 Fedora Update System 2026-11-20 22:09:09 UTC
FEDORA-2026-367bb6f4c3 (musescore-4.7.7-2.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-367bb6f4c3

Comment 17 Fedora Update System 2026-11-21 02:10:48 UTC
FEDORA-2026-47878747a8 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-47878747a8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-47878747a8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2026-11-21 02:33:58 UTC
FEDORA-2026-367bb6f4c3 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-367bb6f4c3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-367bb6f4c3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.


Note You need to log in before you can comment on or make changes to this bug.