MuseScore 3 works with -s only
After upgrade to MuseScore 3 it keeps on crashing (Segmentation fault) whenever it tries to initialize audio - after opening existing score, after creating new score... It works with disabled synthesizer by -s command line switch.
Previous version (not sure which one, but below 3) was working without any issues, no changes to the system configuration, only automatic system-wide update was done.
MuseScore: Music Score Editor; Version 3.0.1; Build 3543170
Linux z800 4.19.23-gentoo #1 SMP Thu Feb 21 23:27:18 CET 2019 x86_64 Intel(R) Xeon(R) CPU E5540 @ 2.53GHz GenuineIntel GNU/Linux
Tested both ALSA and JACK, both crash the same.
When using -s switch, scores open without issues.
Thank you for your support
Rasto
Comments
Why not to test the last version (3.0.4)???
In reply to Why not to test the last… by jotape1960
I'm running on gentoo 64bit and 3.0.1 is the latest available in the repositories. Will try it if everythihng else fails. Thanks.
I suspect your sound driver does not support 64 bit. Try upgrading that and see if you can run it without the -s.
In reply to I suspect your sound driver… by mike320
As far as I know whole system is purely 64bit and audio works in all other software and it was working in previous Musescore version. Any other ideas please?
Thanks.
In reply to As far as I know whole… by Rastislav Tichý
A large number of programs are actually 32 bit. This is because they are compatible for more users. There are 32 bit versions of windows 10, and most programs that say they are compatible with Windows 10 are 32 bit for this reason. I suggest that you have the most current versions of audio drivers that apply to your system. It shouldn't hurt anything else and may help MuseScore. If you prefer, you can install the 32 bit version of MuseScore (the link is below the main link) and see if this fixes it.
Tried everything possible, cannot get the musescore working without -s switch:
(1) found from system logs, my last working configuration (I do not use musescore too often) was kernel 4..14.83 with musescore 2.1.0-r1 - since then I have done weekly gentoo updates and installed java runtime, java sdk and eclipse
(2) I have tried booting the old kernel, downgrading musescore to 2.1.0-r1, upgrading musescore to the latest version available on git
(3) did full recompliation of all gentoo packages - this is almost as reinstalling the system completely
(4) tried varioius modification in ALSA settings in kernel
(5) upgraded all libraries (alsa, qt...) needed for musescore to their latest versions
(6) tried to switch to JACK - musescore will appear in JACK when starting and going through the new score creation wizard, but then it will crash when it is supposed to display the new empty score.
(7) tried external USB soundcard
(8) recompiled musescore with debug flag - I can crash it even with the -s switch, on empty new score, by clicking on the Layout button in the Edit->Debugger window, after selecting Page-1 from the Elements.
Current configuration:
OS: Gentoo/Linux, Arch.: x86_64, MuseScore version (64-bit): 3.0.1., revision: 3543170
Nothing has helped, musescore crashing whenever getting to the point of actually displaying the score (even empty new one) without -s commandline switch. Both internal and external soundcard are correctly recognized by system and working in audacity, firefox, vlc, ardour and multiple software synthesizers and in JACK.
Is there any way to find out what is acutally crashing? I was suspecting audio drivers, but I'm not too sure after the experiments above.
Attaching two console outputs, all with empty new score.
Please help.
Best regards
Rasto