Here is the Build Script: #!/bin/bash
# Save CURA DEPENDS to Documents DIR mkdir ~/Documents/cura cd ~/Documents/cura wget http://ftp.us.debian.org/debian/pool/main/z/z3/libz3-4_4.8.12-3.1_amd64.deb dpkg-deb -x libz3-4_4.8.12-3.1_amd64.deb libz3-4_4.8.12-3.1_amd64 mv libz3-4_4.8.12-3.1_amd64/usr/lib/x86_64-linux-gnu/libz3.so.4 ../cura rm -rf libz3-* # Save CURA to Documents DIR #wget https://github.com/Ultimaker/Cura/releases/download/5.11.0/UltiMaker-Cura-5.11.0-linux-X64.AppImage chmod +x UltiMaker-Cura-5.11.0-linux-X64.AppImage #Launch CURA echo "" echo "Launch CURA using:" echo "" echo "" echo "==> LD_LIBRARY_PATH=~/Documents/cura/ ../Documents/cura/UltiMaker-Cura-5.11.0-linux-X64.AppImage" echo "" echo "" On Mon, Dec 1, 2025 at 11:00 PM Brian Holaday <[email protected]> wrote: > Hello Gregor, > > Using the below github patch I was able to get Cura 5.11 working using the > App Image option. > > Here is what I came up with attached below is a build script. > > Regarding Bug #1121290; there does not seem to be a problem using the App > Image (both the build plate and G-code flavor have options) > > On Tue, 25 Nov 2025 01:23:22 +0100 Gregor Riepl <[email protected]> wrote: > > > Can we please update Cura from 5.0 to 5.11 if possible. > > > > Unfortunately, upstream made some changes to their build process in 5.1 > that prevented us from easily lifting to a newer version. I'm planning to > give it another shot at some point, but I can't promise anything due to > lack of time. > > > > > qt.glx: qglx_findConfig: Failed to finding matching FBConfig for > QSurfaceFormat(version 4.1, options QFlags<QSurfaceFormat::FormatOption>(), > depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, > alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior > QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QColorSpace(), > profile QSurfaceFormat::CoreProfile) > > > Could not initialize GLX > > > AbortedThis looks suspiciously like > https://github.com/Ultimaker/Cura/issues/19837 > > > > Have you tried the workarounds from there? > > > > Someone also mentioned that the flatpack version isn't affected. > > > > >
