How to get Cura appimage running in Bionic 64? Solved

[vtpup]

Hello all, I've tried getting Cura latest version (5.2.1) appimage running on Bionic 64. I've downloaded and tried the two available Linux versions from their main site: https://ultimaker.com/software/ultimaker-cura

The two versions are: one labeled for 64 bit linuxes, and the oother for "modern" 64 bit linuxes. Neither works.

Procedure:
I downloaded both versions, chenged the file permissions for both to executable. Tried just clicking on them. Nothing. Then opened a console window in their directory and tried running each. Then from a reference somewhere from Mike Walsh I also tried a --no-sandbox flag. Still no go. All error messages:

Code: Select all

root# ./Ultimaker-Cura-5.2.1-linux.AppImage
 [1379] Error loading Python lib '/initrd/mnt/tmpfs/tmp/.mount_UltimadvniMo/libpython3.10.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /initrd/mnt/tmpfs/tmp/.mount_UltimadvniMo/libpython3.10.so.1.0)

root# ./Ultimaker-Cura-5.2.1-linux-modern.AppImage
[3824] Error loading Python lib '/initrd/mnt/tmpfs/tmp/.mount_Ultima4yZ2d1/libpython3.10.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /initrd/mnt/tmpfs/tmp/.mount_Ultima4yZ2d1/libpython3.10.so.1.0)

root# ./Ultimaker-Cura-5.2.1-linux-modern.AppImage --no-sandbox
[4897] Error loading Python lib '/initrd/mnt/tmpfs/tmp/.mount_UltimaCtQPP0/libpython3.10.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /initrd/mnt/tmpfs/tmp/.mount_UltimaCtQPP0/libpython3.10.so.1.0)

Bionicpup64 has latest updates, and the computer is the Acer laptop listed in my sig, but in this instance running Bionic, not Fossa.

[mikewalsh]

@vtpup :-

From the output, it wants a newer Glibc. Simple as that.

It'll probably run fine under Fossa64, but Bionic64 - on this version, at least - is a no-go. The oldest referenced version is 2.29.....that's around the time of Disco Dingo, or newer; approximately midway between Bionic and Fossa.

Bionic uses Glibc 2.27.

Does the site have any links to older versions?

------------------------------------------

EDIT:- Okay; if you want to run this in Bionic, I reckon you'll need to go with the final release of the 4-series, v4.13.1:- https://github.com/Ultimaker/Cura/relea ... 1.AppImage

(I'm just running these from the terminal.....I'm in Barry's old Quirky April here - glibc 2.20! - not a hope in hell it'll run, but the terminal can still tell me what's what. v4.13.1 references as far back as glibc 2.25, but it looks like they upgraded their build environment to require a minimum of glibc 2.29 with the move to the 5-series.)

Just FYI.

Mike.

[vtpup]

Thanks Mike,

I tried it in Fossa and the non-"Modern" linux version did open, but unfortunately was unusable because it couldn't open a project file -- or any files.

So I, like you found some older versions on github and tried the 4.3 version (at random) in Bionic, and it opened fine and does seem to be able to open files also.

I'll try 4.13 on your suggestion......

Thanks so much for your help!

[vtpup]

Mike 4.13.1 is too new for my Bionic64 version, but the 4.3 version does seem to be fully functional, and that probably will suit my pretty simple needs.

I might try a few versions in between just out of curiosity to see the what the latest version Bionic can handle is. Though with our slow download speed it's painful to try a lot of them.

If I do, I'll report back.

But solved as far as I'm concerned, as is.

Thanks again!

[mikewalsh]

@vtpup :-

Good, good. The main reason I took an interest in this is because I ran up some early packages of Cura for someone else a few years back when 3D printing was just starting to take off. I'd completely forgotten about it until I saw you mention it!

In the early days it wasn't an AppImage at all; just a self-contained tarball, and it needed a number of other things adding to it to make it fully functional. But, from the look of things, they've got virtually the entire history of the app there at Github, so it was only ever going to be a case of gradually working your way back till you found one that did work.

Glad to hear you're sorted. At least you know where to find the packages now.

Mike.