Package Details: cura-git 4.5.0.r192.g44b61d370-1

Git Clone URL: (read-only, click to copy)
Package Base: cura-git
Description: A full software solution for 3D printing aimed at RepRaps and the Ultimaker.
Upstream URL:
Keywords: 3dprint cura ultimaker
Licenses: GPL3
Conflicts: cura
Provides: cura
Submitter: ad1217
Maintainer: ad1217 (greyltc)
Last Packager: ad1217
Votes: 13
Popularity: 0.110665
First Submitted: 2014-11-24 06:53
Last Updated: 2020-03-19 21:48

Pinned Comments

ad1217 commented on 2018-02-14 18:10

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
to rebuild this and all related packages.

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.

Latest Comments

1 2 3 4 5 Next › Last »

Forsaken commented on 2020-06-15 17:27

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

lewis2e commented on 2020-04-10 06:29

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

linkeb3 commented on 2020-04-10 03:58

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.

lewis2e commented on 2020-04-02 11:34

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

lewis2e commented on 2020-04-02 11:25

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

ad1217 commented on 2020-03-19 21:47

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

lewis2e commented on 2020-03-19 20:27

@ad1217 - Have pasted here:

Hope it helps.

ad1217 commented on 2020-03-19 20:20

@lewis2e: Can you either email or post the contents of ~/.local/share/cura/master/cura.log?

lewis2e commented on 2020-03-19 19:18

@ad1217 Thanks, have tried this. Re-building the packages did not change anything (I uninstalled, installed (clean build) and then re-built just for good measure). I have tried on both my laptop and my desktop (running Arch) - both have the same issue. Happy to send you log files, but would need guidance on what you need.

From the thread that I linked, it sounds like its a QT library issue. That's the exact issue I am having. The button to proceed with the wizard is missing.

ad1217 commented on 2020-03-19 18:15

@lewis2e: I can't replicate this issue, could you try rebuilding all the related packages (check the pinned comment for a list), and if that doesn't work, send me a log? I might be missing a dependency in the package.