Package Details: cura-bin 5.7.2-2

Git Clone URL: https://aur.archlinux.org/cura-bin.git (read-only, click to copy)
Package Base: cura-bin
Description: State-of-the-art slicer app to prepare your 3D models for your 3D printer
Upstream URL: https://ultimaker.com/software/ultimaker-cura
Licenses: LGPL3
Conflicts: cura
Provides: cura
Submitter: prurigro
Maintainer: prurigro
Last Packager: prurigro
Votes: 46
Popularity: 2.75
First Submitted: 2022-09-02 21:14 (UTC)
Last Updated: 2024-06-28 15:55 (UTC)

Latest Comments

1 2 3 4 5 6 .. 16 Next › Last »

Dirk commented on 2024-06-29 10:34 (UTC)

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

prurigro commented on 2024-06-28 15:56 (UTC) (edited on 2024-06-28 15:57 (UTC) by prurigro)

@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

sausix commented on 2024-06-28 10:03 (UTC)

@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.

xubz commented on 2024-06-23 05:27 (UTC)

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.

Dirk commented on 2024-06-13 08:26 (UTC)

@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.

sausix commented on 2024-06-11 09:07 (UTC)

@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.

Dirk commented on 2024-06-11 08:29 (UTC) (edited on 2024-06-11 08:32 (UTC) by Dirk)

@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.

prurigro commented on 2024-06-11 01:31 (UTC)

@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

sausix commented on 2024-06-10 21:45 (UTC)

I give up. Downgrading mesa helps at least for now. I could not find any magic environment variables. Not even for letting cura print some debug information.

Cura runs on PyQt6 and at least my own PySide6 programs also threw EGL warnings too. Cura still depends on Python 3.11 and also sticks to a 3 year old numpy version. Could not get it to run from github without installing Python 3.11. Of course these apps break on Arch Linux first.

@Dirk You did not have the model itself visualised? People using NVidia and pure Wayland had a white screen except the menu and toolbar without the patch applied. The plane was missing. The visualised print bed is probably an extra feature if it's avalable in the app.

Dirk commented on 2024-06-08 19:54 (UTC)

@sausix I never had the print bed or model visualized. only the plane with the coordinates indicator and being in reverse order when visualized (or printed?), Ender 5 Pro.

Not on X11 nor Wayland, not with the installed version, nor with the “manually installed” AppImage, nor with this AUR package …