MuseScore 4.5 Opens and Then Closes (Linux)
I am having an issue wherein my MuseScore, which I had been using on my Linux distro has stopped working. It opens and closes immediately and the log files (attached) don't provide much information. It does this regardless if it the appimage, flatpak, or the one given by my Distro. It crashes with Wayland and X11. The appimage did work twice and then stopped. Has anyone else had this issue?
My System:
OpenMandriva 25.04 (ROME)
Kernel: Linux 6.13.5
WM: KWin (Wayland or X11)
CPU: AMD Ryzen 9 6900HX
Memory: 24G DDR5
Thank you for any assistance possible!
| Attachment | Size |
|---|---|
| MuseScore Log File.txt | 28.7 KB |
Comments
Just an update here, in case anyone has also had this issue or can make a suggestion...
I have also downloaded and tried older appimage versions from the 3.x and 2.x releases of MuseScore and those do not even try to open.
In reply to Just an update here, in case… by Matt Williams4
I was thinking it was a QT framework incompatibility, but if you're having issues with prior versions, I don't know. Here's a link to a thread comment when QT incompatibility was the issue and fixed.
https://musescore.org/en/node/370213#comment-1263269
It might be interesting to see the log files for 3.x.
Mandriva might be the basis of our problem. There's very little info on using MuseScore with Mandriva. Here's a thread from 15 years. Not encouraging.
https://musescore.org/en/node/3892
In reply to I was thinking it was a QT… by daveburkevt
I've been struggling getting MuseScore to work properly for a few days now. From my experiences, I think it might be that many of the artifacts are compiled against glibc 3.4. I've tried the appimage, flatpak, and also the Muse_Sounds_Manager_Beta.rpm without success on AlmaLinux 9. Most result in some sort of error about not finding glibc 3.4 something like:
nothing provides libstdc++.so.6(GLIBCXX_3.4.30)(64bit) needed by muse-sounds-manager-1.1.0.587-1.x86_64 from @commandlineThe flatpak version will run, but many things don't work, notably the mixer will not display as well as several other tools. The appimage will not run at all as it can't find the system depenecy on glibc 3.4, and the rpm simply will not install. A quick look at pkgs.org shows me that most distro's are still on glibc 2.34 or something close to it. I think the MuseScore artifacts are compiled on a mainline kernel version 6 or higher with glibc version 3.4 or higher so that they will not run on most distros unless they run an unsupported mainline kernel from their distro.
The log warns about:
Could not create EGL surface (EGL error 0x3000)Although it is only a warning...
MAYBE you're missing system egl libraries, on my system I have:
libegl-mesa0:amd64
libegl1:amd64
libwayland-egl1:amd64
A known trick/workaround for Musescore 4 graphical issues is to set:
export QT_QUICK_BACKEND="software"before starting musescore.
In reply to The log warns about: Could… by larryz
Ok - thank you for that tip. It turns out that there were a few issues on my system, and your tip led me down the rabbit's hole of fixing the issue. I worked with Grok, which led me through an entire process. OpenMandriva's package is actually wrong (I will let them know) and installs MuseScore Development 4.4.4, not 4.5. Also, there are multiple QT errors. So in order to get 4.5 to run I manually downloaded the flatpak and then forced it to run in an X11 Session per Grok's instructions (below). It now loads just fine. I'll share below some of the instructions I followed to get it to work:
(FROM GROK)
Looks like MuseScore 4.5 (Flatpak) is failing to start because of a Qt platform plugin issue tied to Wayland. The error Failed to create wl_display (No such file or directory) and Could not load the Qt platform plugin "wayland" suggest it’s trying to use Wayland (KDE 6.3.4’s default on OpenMandriva 25.04) but can’t initialize it. This could be a Flatpak sandboxing quirk or a missing Wayland dependency. Let’s get it running.
What’s Happening
Wayland Failure: MuseScore’s Qt backend wants to use Wayland (wl_display is Wayland’s display server), but Flatpak’s sandbox might not have access to your system’s Wayland session.
Plugin Error: Qt can’t load the “wayland” plugin, even though it’s listed among available plugins (wayland, wayland-egl, etc.). This could mean a misconfiguration or missing runtime support.
Fallback Options: Qt lists other plugins like xcb (X11) and eglfs (EGL fullscreen), which we can force to bypass Wayland.
Fixing It
Since it’s crashing on startup, we’ll try forcing a different Qt platform plugin and tweak the Flatpak environment.
Your system likely supports X11 alongside Wayland (KDE 6.3.4 often runs on X11 by default unless you chose Wayland). Tell Qt to use xcb:
flatpak run --env=QT_QPA_PLATFORM=xcb org.musescore.MuseScore
If this works, MuseScore will run on X11, avoiding Wayland issues.
Check your session type first:
echo $XDG_SESSION_TYPE
If it says x11, this should work out of the box. If it’s wayland, you might need to log into an X11 session via your display manager (e.g., SDDM).
Your original EGL issue might still apply. Combine it with xcb:
flatpak run --env=QT_QPA_PLATFORM=xcb --env=QT_QUICK_BACKEND=software org.musescore.MuseScore
This forces X11 and software rendering, dodging both Wayland and hardware EGL problems.
3. Fix Wayland (Optional)
If you prefer Wayland (and $XDG_SESSION_TYPE confirms it), the Flatpak sandbox might need Wayland socket access. Check:
ls /run/user/$(id -u)/wayland-*
If you see /run/user/1000/wayland-0 (or similar), Wayland is active. Flatpak should auto-mount this, but if not, try:
flatpak run --socket=wayland org.musescore.MuseScore
If it still fails, Wayland support in Flatpak’s Qt might be broken with your Mesa/KDE setup.
4. Reinstall Flatpak (Fallback)
The error suggests reinstalling might help. It’s worth a shot:
flatpak uninstall org.musescore.MuseScore
flatpak install flathub org.musescore.MuseScore
Then retry:
flatpak run org.musescore.MuseScore
If none work, get more Qt debug output:
flatpak run --env=QT_DEBUG_PLUGINS=1 org.musescore.MuseScore
This will spew details about why the plugin fails—share that if it comes to it.
Quick Checks
Session Type: echo $XDG_SESSION_TYPE (Wayland or X11?).
Mesa/Wayland Libs: Ensure Wayland support is installed:
rpm -qa | grep -i wayland
Look for lib64wayland-client, lib64wayland-egl, etc. Install if missing:
sudo dnf install lib64wayland-client lib64wayland-egl
What to Try Now
Run flatpak run --env=QT_QPA_PLATFORM=xcb org.musescore.MuseScore and see if it launches.
If it crashes, try the combined xcb + software command.
Check echo $XDG_SESSION_TYPE and let me know (Wayland/X11).
If it works, you’re set! If not, share any new errors, and we’ll crack it.