MuseScore AppImage crash when change settings to JACK or from JACK

• Jul 11, 2019 - 15:56
Reported version
3.3
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

  1. Install the most recent nightly appimage on Fedora 30 (Workstation Edition), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.23055, revision: fa50dff from https://musescore.org/en/node/add/project_issue?pid=1236. My platform is fedora 30, my kernel is 5.1.17-300.fc30.x86_64.

  2. Problem: musescore-2.2 usus jack for I/o, but the nightly wont. Switch to this I/o method lets the nightly die (saying apply or OK) after using Jack as I/O method) with the error msg

/tmp/.mount_vg56V6/AppRun: line 28: 5606 Segmentation fault (core dumped) "${APPDIR}/bin/mscore-portable-nightly" "$@".

What I seeing in the terminal is

ack appears to be installed on this system, so we'll use it.
QApplication: invalid style override passed, ignoring it.
ALSA lib pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Comments

• Dec 14, 2020 - 16:21
Title musescore nightly dies if using Jack as I/O method ⇒ musescroe 3.5.2 appimage crash when setting jack
Frequency Few ⇒ Many
Severity S4 - Minor ⇒ S2 - Critical
Reported version 3.x-dev ⇒ 3.5

This prevents users to work with the software and produces significant problems

Reply

• Mar 17, 2021 - 04:49
Title MuseScore AppImage crash when setting JACK ⇒ MuseScore AppImage crash when change settings to JACK or from JACK

I can verify the crash with MuseScore-3.6.2.548021370-x86_64.AppImage on Arch Linux 5.11.2-rt9. Though I can create the crash both when changing from PulseAudio to Jack, and I can create the crash when changing from Jack to PulseAudio. However, if my MuseScore preferences were already set to Jack before I started the AppImage, then I am able to use Jack with the AppImage just fine...and I'm also able to change MuseScore's jack settings (i.e. checking and unchecking the different checkboxes under the Jack tab).

So I'm going to change the title to more specifically "Crash when change settings to JACK or from JACK"

Has there been any attempts at fixing this, or should I give it a shot?

Reply

• Mar 17, 2021 - 05:08
Workaround No ⇒ Yes

workaround is manually change your preferences.ini file section [io] to disable Alsa & Pulse and enable jack prior to starting MuseScore, like so:

[io]
alsa\useAlsaAudio=false
jack\useJackAudio=true
portAudio\usePortAudio=false
pulseAudio\usePulseAudio=false

Then you should be able to start MuseScore AppImage with jack, and can change the other Jack settings. And if you want to leave jack, then restore the [io] settings from your initial preferences.ini file.

Reply

• Mar 17, 2021 - 07:22

I believe with command line options you can do those switches too:

-a | --use-audio driver

Use audio driver: one of jack, alsa, portaudio, pulse

so -a jack should do I guess

Reply