Package Details: cura-bin 5.8.1-1

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: 49
Popularity: 1.36
First Submitted: 2022-09-02 21:14 (UTC)
Last Updated: 2024-09-01 03:04 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 16 Next › Last »

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 …

sausix commented on 2024-06-08 13:04 (UTC)

Seems to affect older packages too. So unfortunately downgrading cura-bin doesn't help. Definitely affects the nvidia patch and by removing we end up having no print bed and model visualized.

prurigro commented on 2024-06-07 15:41 (UTC) (edited on 2024-06-07 15:44 (UTC) by prurigro)

@Sadam: I'm getting this too- it seems like this was an issue a while back and was resolved with the "modern" AppImage, but that no longer exists... It can temporarily be worked around by launching with QT_QPA_PLATFORM=xcb, but that's not an optimal solution.

Edit: It can also be worked around by downgrading mesa to 1:24.1.0

Sadam commented on 2024-06-07 08:15 (UTC)

Does not work after system update, crashes with "Could not probe OpenGL. This program requires OpenGL 2.0 or higher. Please check your video card drivers." (And yes my OpenGL is working Radeon RX 7700 XT / 7800 XT)

saliherdemk commented on 2024-05-24 09:05 (UTC)

Can confirm @bitdrifter 's solution. Disabling Usb Printing seems to resolve the issue.

Dirk commented on 2024-05-21 10:28 (UTC) (edited on 2024-05-21 10:28 (UTC) by Dirk)

That’s a nice trick, thank you. Disabling the USB printing plugin seems to work.

Disabling USB printing: The model is instantly loaded with providing it as parameter, via drag&drop, and via manually opening it through the menu.

Enabling it again: Behavior as previously discussed.

Disabling again: loading models works without delay.

bitdrifter commented on 2024-05-21 05:02 (UTC)

@Dirk: I had the problem that opening took very long until (for example STL) the file was imported. I only use octoprint and did not connected the printer directly to my pc. Aftert looking in cura log ($HOME/.local/share/cura/5.7/cura.log) I realized many tries to connect to any serial port. So I disabled the USB plugin in Cura and it worked after that normal again. You can disable it via: Marketplace -> Settings Icon on top right -> "USB Printing". Maybe this helps somebody.

Dirk commented on 2024-05-21 04:14 (UTC)

I need the script solely for running it with the platformtheme parameter without having to provide it every time I start Cura because of this behavior. Without this parameter I can’t open files at all.

I never really cared about AppImages. But downloading and starting the one from the Ultimaker website does not work at all (to print bed shown, opening files does not work). Naively adding -platformtheme gtk3 to the AppImage call seems not to work. So I cannot test, sorry.

prurigro commented on 2024-05-20 19:00 (UTC)

@Dirk: Does running the AppImage also have this issue, and is that local/bin script fixing the issue for you?