i686 AppImage crash
Using MuseScore-2.1-i686.AppImage on an ancient laptop with a lightweight OS named BunsenLabs 8.9 bunsen-hydrogen - Kernel: i686 Linux 3.16.0-5-586 - Shell: bash 4.3.30
- DE: XFCE - WM: OpenBox.
It crashes all the time.
As soon as I execute it again it suggests to recover last session, which it does, but then only stays alive for a minute or 2 at the most.
Comments
Is there any output if you start the AppImage from terminal? Be sure, that you've downloaded the correct version for your system (32bit or 64bit).
In reply to Is there any output if you… by kuwitt
Here it is:
ludo@lbbunsen:~/bin$ MuseScore-2.1-i686.AppImage
initScoreFonts 0x9c23d18
/tmp/.mount_UynC3W/AppRun: line 18: 11660 Segmentation fault "${APPDIR}/bin/mscore-portable" "$@"
In reply to Here it is:… by catch22
I never used MuseScore on a 32bit system, so I can't give much suggestion therefore.
I always download the AppImage into the download folder of my home directory and had never problems until now.
Maybe try to start MuseScore with some command line options like "-F" or other.
Or check if there's a graphic driver problem: https://musescore.org/en/node/265128
You say you are on "Kernel: i686", but then immediately afterwards you say "Linux 3.16.0-5-586". Did you know that the "5" in "586" stands for Intel "Pent"ium architecture? That came before the 686 architecture for the Intel Pentium-Pro released in 1995. There are many differences between 586 and 686...in particular as https://packages.debian.org/jessie/linux-image-3.16.0-5-586 explains, that kernel you are using lacks PAE (Physical Address Extension). That is very likely to cause a crash if some pointers are assuming the existence of PAE.
In reply to You say you are on "Kernel:… by ericfontainejazz
Thanks for spotting that!
I guess it also explains why the package manager of the OS can't find anything more recent than Musescore-1.3.
I guess I'll have to try and work with that old version then.
Thank you all for the help in solving the mystery.
In reply to Thanks for spotting that!… by catch22
well the reason why your package manager can't find anything more recent than MuseScore 1.3 is because BrunsenLabs 8.9 (hydrogen) is based on Debian Jessie. And Debian Jessie only has MuseScore 1.3 in its repos.
The question of 586 non-PAE versus 686 with-PAE is orthogonal. Hypothetically maybe MuseScore should have produced a 586 version for maximum compatibility. But since we haven't, unfortunately you are stuck with what Debian Jessie provides, unless you upgrade your distro.
In reply to well the reason why your… by ericfontainejazz
And upgrade the distro will turn 586 non-PAE into 686 with-PAE?
In reply to And upgrade the distro will… by Jojo-Schmitz
A simple apt dist-upgrade won't change from non PAE to PAE. That would probably require a reimstall.
Not sure I understand your question.
In reply to A simple apt dist-upgrade… by ericfontainejazz
You claimed that after an upgrade od the distrro the OP would be able to find and use MuseScore 2.x, which does require 686 PAE. Apparently it does not, as your answer to my questions seems to indicate
In reply to You claimed that after an… by Jojo-Schmitz
Oh.
I was thinking the original problem was because the AppImage was built in an 686 w/ PAE environment and therefore can't run on distros without PAE. I don't know if 2.x necessarily does require PAE, but if it does, than simply upgrading the distro won't help.
In reply to well the reason why your… by ericfontainejazz
Installing without PAE was difficult enough.
It's only temporarily that I'm stuck with this machine, so I'll live with it as is for now.