Arch Linux User Repository

Here is a patch to add url handler support to the desktop file so you can open directly from Thingiverse

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -39,7 +39,8 @@
   cd squashfs-root
   sed -i 's|^Comment=.*|Comment=Cura converts 3D models into paths for a 3D printer. It prepares your print for maximum accuracy, minimum printing time and good reliability with many extra features that make your print come out great.|' com.ultimaker.cura.desktop
   sed -i 's|^Icon=|Icon=/usr/share/pixmaps/|' com.ultimaker.cura.desktop
-  printf '%s\n' 'MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;image/bmp;image/gif;image/jpeg;image/png;text/x-gcode;application/x-amf;application/x-ply;application/x-ctm;model/vnd.collada+xml;model/gltf-binary;model/gltf+json;model/vnd.collada+xml+zip;' >> com.ultimaker.cura.desktop
+  sed -i '/^Exec=/ s/$/ %U/' com.ultimaker.cura.desktop
+  printf '%s\n' 'MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;image/bmp;image/gif;image/jpeg;image/png;text/x-gcode;application/x-amf;application/x-ply;application/x-ctm;model/vnd.collada+xml;model/gltf-binary;model/gltf+json;model/vnd.collada+xml+zip;x-scheme-handler/cura;' >> com.ultimaker.cura.desktop
   printf '%s\n' 'Keywords=3D;Printing;' >> com.ultimaker.cura.desktop
   patch -p1 < ../AppRun.env.patch
 }

I ran into an issue with the USB Printing plugin that delays the loading of STL files quite a bit. Here's the workaround for now :) https://github.com/Ultimaker/Cura/issues/16249#issuecomment-2094405826

I can confirm that the fix works.

cura-bin   5.7.2-2
flatpak    1:1.15.8-1
mesa       1:24.1.2-1
wayland    1.23.0-1
labwc      0.7.2-1
nvidia     550.90.07-4

@sausix: Yup, that was me over there :) Thanks for figuring out that deleting the libwayland-client.so.0 would fall back on the system version and fix the issue! I've updated the package with your tweak (+ credited you) and things are working again with the official mesa package.

I also opened a ticket here https://github.com/Ultimaker/Cura/issues/19303

@prurigro Something was going on in the mesa bugtracker!

Deleting /opt/ultimaker-cura/libwayland-client.so.0 seem to fix the issue. The AppImage seems to ship a build against an older wayland-client. By deleting this file the app uses the one shipped with Arch Linux.

Works with newest mesa 24.1.2 for me.

Strange, but expected I guess.

With nvidia-beta drivers and Plasma 6.1 (both supporting Explicit Sync) and latest mesa, I no longer get the flickering mess when using QT_QPA_PLATFORM=xcb

Works fine even after removing __EGL_VENDOR_LIBRARY_FILENAMES & MESA_LOADER_DRIVER_OVERRIDE flags from the executable script.

I guess we just need to wait for the official nvidia stable drivers and everything will be fine.

@sausix Ah, good to know. I thought of some weird rendering order/sorting issues. That's fine then, I guess. Thanks!

Right now the only sane thing is to downgrade Mesa since Xwayland is close to unusable on Nvidia.

@prurigro Thanks! I struggled with opening an issue in mesa. Complicated topic and hard to provide examples.
QT_QPA_PLATFORM=xcb breaks things for NVidia users introducing heavy flickering. Just tested. With downgraded mesa still applies.

@Dirk It's probably not a graphics problem. Your printer just hasn't a STL model provided in Cura.

@sausix I get the coordinates and the base visualized, and the model I want to print. But neither get I a printer-specific print bed visualization nor do I get the printer frame. It always was like that for me.

Since I currently force using Xwayland because of the OpenGL error message bug I cannot say if this works on Wayland, but before that bug (i.e. in previous versions) I also never had anything printer-specific shown, but only the plain and simple coordinates indicator in the wrong direction and the generic print bed surface.

@sausix: QT_QPA_PLATFORM=xcb will work, but it makes the app run in xwayland. I like you am just keeping mesa downgraded for now.

The issue also happens with the latest git master of mesa so I opened an issue here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11316