Crash when adding a synth track with DeicsOnze/FluidSynth/Organ/vam

[BMuXBeats]

Describe the bug
Muse crashes immediately when adding a synth track with DeicsOnze/FluidSynth/Organ/vam.

To Reproduce
Steps to reproduce the behavior:

Right-click on the mouse
In "Add Track"', choose "Synths"
In the list, select "DeicsOnze/FluidSynth/Organ/vam MESS"
Click on the "Select" button

Expected behavior
I expected the track to be created flawless.

Desktop (please complete the following information):

• OS: LINUX Manjaro
• Release: 23.1.2 /Codename: Vulcan
• Kernel: Kernel: 6.6.8-2-MANJARO x86_64
• DEsktop Environment: KDE-Plasma Version 5.27.10

Additional context

• Muse 4.2.1 (Manjaro official software repository)

[rdvdev2]

Same problem here.

My setup:

• OS: Arch Linux
• Release: Rolling release, last update today (September 22nd 2024)
• Kernel: 6.10.10-zen1-1.1-zen
• Desktop Environment: GNOME 47 (Wayland)
• Muse version: 4.2.1 (packaged here)

[terminator356]

Hello. Sorry for the verrry late reply.

I read Manjaro is based on Arch.
Thus it's... Arch's fault?

This bug sounds strange because those synths are MusE's own MESS synths and shouldn't have
any trouble at all since they should have been compiled at the same time as MusE.

Thanks for the backtrace, it does not seem to appear here, but in my email.
Unfortunately I can't view it properly unless I run your distro. I've no partitions left.

You could try running MusE in a terminal with -D to get some debugging info. "muse4 -D"
Post what you find.

Thanks.

[oznogon]

This is consistently reproducible for me on Fedora 41 x86_64 running KDE Plasma 6.2.5, Linux kernel 6.12.9, with MusE 4.2.1 installed from the official Fedora repos. No output when the crash occurs when running muse4 -D beyond the segfault.

Notably, this does not affect the AppImage version of 4.2.1 for me, which works fine.

(this might be another duplicate of #1245/#1253)

[terminator356]

Hi thanks for the report.
Running opensuse tumbleweed rolling distro here.
I've not seen anything to date like this.
Seems maybe the way it's being packaged or compiled?

Could try compiling from release source.
Hopefully would be ok then.