Arch Linux User Repository

This is a VCS package, which means that when you build it, it will set the pkgver based on the latest version in the upstream repo. The only thing bumping version numbers here does is make people who already have it installed see that it needs updating (assuming they use an AUR helper). Bumping it here frequently is both pointless, as anyone can just rebuild the package(s) to get the latest, and annoying, since the git repo updates many times a day. If you want to get the latest, I'd suggest running something like

<your-AUR-helper> -Sy {cura-fdm-materials,cura-binary-data,curaengine,libarcus,uranium,cura}-git

Generally, I will only update these packages when something changes in the build process such that they don't work, dependencies change, or a major version is released.

After a recent update this week cura no longer opens:

Traceback (most recent call last):
  File "/usr/bin/cura", line 23, in <module>
    import Arcus  # @UnusedImport
ModuleNotFoundError: No module named 'Arcus'

I'm not actually sure how to fix this one

@uncholowapo: Should be fixed now, thanks for the heads up!

Got this error when starting Cura that was compiled today. Looks like neither the libnest2d lib nor the python binding are in the official repos nor in AUR

Traceback (most recent call last):
  File "/usr/bin/cura", line 25, in <module>
    import pynest2d # @UnusedImport
ModuleNotFoundError: No module named 'pynest2d'

When running into an error message like this one (usually appears after an update of profobuf):

Traceback (most recent call last):
  File "/usr/bin/cura", line 23, in <module>
    import Arcus  # @UnusedImport
ImportError: libprotobuf.so.22: cannot open shared object file: No such file or directory

Make a clean build of the libarcus-git, which should solve the issue. I made a clean build of cura-git first while searching for a solution, so maybe you have to rebuild both.

Edit: if in doubt you can use the command mentioned in the pinned comment and clean build all dependencies, to make sure you got the offending package.

@linkeb3 it does. No resolution I'm afraid. I'm using the official appimage version.

Graphical issues on launch, i can tab space/enter a few menu's forward, but it'll stall when selecting a printer.

@lewis2e any resolution? sounds like the same issue i've got.

@ad1217 So, clearing my config files as you suggested means that the community version of Cura has the same issue at this one - i.e. stuck in the wizard, no option to click to continue.

The screenshot I previously posted is before I cleared the config files. So - the existing config means no wizard, and Cura starts up. But graphical problems.

I think it's all the same problem with both the community package and this Git version. Something to do with the QT libs as per that link I posted.

The only version I can get to behave is the appimage version.

@ad1217 Sorry, to answer your question, using the normal community Cura package gives me some ...different... graphical errors. Again, this is the same on both my desktop and laptop computers (Nvidia and Intel graphics respectively - both Arch).

Illustration - https://pasteboard.co/J1W572V.png

@lewis2e: Well, reading through your log and trying to replicate in a clean VM didn't yield any answers. The only other ideas I have are to make sure your whole system is up to date, and try resetting your Cura config (rm -rf .config/cura .local/share/cura). Also, have you tried the normal community/cura package?

@ad1217 - Have pasted here: https://pastebin.com/zBWkftQ1

Hope it helps.