musescore / musescore/MuseScore

MuseSampler fails to initialize on non-systemd Linux distributions

Open
#32,911 5 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Apr 4, 2026.

needs review os: linux playback
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Description with steps to reproduce

I created the following VMs:

  • Fedora 43 (systemd)
  • Void (runit)
  • Artix (openrc)

All 3 VMs were running KDE Plasma and a Wayland session.

I started the process by downloading MuseSounds Manager (TAR) and the MuseScore Studio AppImage. I then:

  1. Launched MuseSounds Manager and installed the same sound on all 3 VMs.
  2. Exited
  3. chmod +x ./MuseScore-Studio-4.6.5.*.AppImage
  4. ./MuseScore-Studio-4.6.5.*.AppImage
  5. Verify

Only the Fedora 43 VM worked as expected.

Supporting files, videos and screenshots
MuseSamplerLibHandler::init | Could not init lib
MuseSamplerResolver::init | Could not init MuseSampler: /home/<username>/.local/share/MuseSampler/lib/libMuseSamplerCoreLib.so, version: 0.105.1
In which versions of MuseScore Studio is this issue present?

4.x

Regression

No.

Operating system

Linux (non-systemd)

Additional context

After a lot of searching I found this which seems to be relevant: https://musescore.org/en/node/387066

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.