Bug 2404987

Summary:	MuseSamplerLibHandler Could not init
Product:	[Fedora] Fedora	Reporter:	cornosier
Component:	musescore	Assignee:	Jerry James <loganjerry>
Status:	ASSIGNED ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	43	CC:	lminiero, loganjerry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.