Package Details: cura-git 4.8.beta.r99.g5ab4062ce-1

Git Clone URL: https://aur.archlinux.org/cura-git.git (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: https://github.com/Ultimaker/Cura
Keywords: 3dprint cura ultimaker
Licenses: GPL3
Conflicts: cura
Provides: cura
Submitter: ad1217
Maintainer: ad1217 (greyltc)
Last Packager: ad1217
Votes: 13
Popularity: 0.000001
First Submitted: 2014-11-24 06:53 (UTC)
Last Updated: 2020-11-09 02:19 (UTC)

Pinned Comments

ad1217 commented on 2018-02-14 18:10 (UTC) (edited on 2020-03-01 18:53 (UTC) by ad1217)

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

vanja_z commented on 2022-01-03 16:16 (UTC)

I could not build the package today because I was getting the error,

include could not find load file:

UraniumTranslationTools

I tried rebuilding all of the VCS package dependencies including uranium-git but it did not help. The problem is that uranium-git places UraniumTranslationTools.cmake into /usr/share/cmake-3.22/Modules which is an otherwise empty directory. All of the other cmake modules in my system are located in /usr/share/cmake/Modules so as a workaround I created a symlink.

sudo ln -s /usr/share/cmake-3.22/Modules/UraniumTranslationTools.cmake /usr/share/cmake/Modules/UraniumTranslationTools.cmake

My question is, what is the correct location for cmake modules? On my system there is nothing other than the aforementioned file under /usr/share/cmake-3.22 and everything else is simply under /usr/share/cmake. Is this a bug that should be reported upstream to uranium devs? Or is it a packaging issue specific to Arch that we should take care of with the AUR package uranium-git?

Thanks, Vanja

Meganium97 commented on 2021-10-04 19:55 (UTC)

I'm not able to install, getting the error: File "/usr/bin/cura", line 21, in <module> from UM.Platform import Platform ModuleNotFoundError: No module named 'UM'

What do I need to do?

VanClaussen commented on 2021-07-23 12:56 (UTC)

cura-fdm-materials-git isn't an optional dependence because you can't use cura without it (can't create materials or options for materials).

a36233 commented on 2021-04-21 11:06 (UTC)

python-keyring dependency missing

stratus_ss commented on 2020-12-11 23:57 (UTC)

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

ad1217 commented on 2020-11-09 02:21 (UTC)

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

uncholowapo commented on 2020-11-08 14:01 (UTC) (edited on 2020-11-08 14:03 (UTC) by uncholowapo)

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'

Forsaken commented on 2020-06-15 17:27 (UTC) (edited on 2020-06-15 17:33 (UTC) by Forsaken)

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.

lewis2e commented on 2020-04-10 06:29 (UTC) (edited on 2020-04-10 06:29 (UTC) by lewis2e)

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

linkeb3 commented on 2020-04-10 03:58 (UTC) (edited on 2020-04-10 04:00 (UTC) by linkeb3)

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 (UTC) (edited on 2020-04-02 11:35 (UTC) by lewis2e)

@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 (UTC)

@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

ad1217 commented on 2020-03-19 21:47 (UTC)

@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 (UTC)

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

Hope it helps.

ad1217 commented on 2020-03-19 20:20 (UTC)

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

lewis2e commented on 2020-03-19 19:18 (UTC)

@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 (UTC)

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

lewis2e commented on 2020-03-19 13:29 (UTC)

I am getting the issue described here, whereby the software is stuck at the welcome screen: https://community.ultimaker.com/topic/28928-cura-41-stuck-at-welcome-screen-buttons-are-missing/ Going to have to use the AppImage version instead.

remspoor commented on 2020-01-01 13:56 (UTC)

As i wanted to know if the preview function crashes cura by installing this -git version i stumbled upon this error when starting:

Traceback (most recent call last):
  File "/usr/bin/cura", line 15, in <module>
    import sentry_sdk
ModuleNotFoundError: No module named 'sentry_sdk'

This was solved by installing aur/python-sentry_sdk maybe consider adding the dependency.

ad1217 commented on 2019-12-05 04:07 (UTC)

@m1tch Added to the appropriate packages. Thanks for the heads up!

m1tch commented on 2019-12-04 15:58 (UTC)

To be able to run cura I needed to install python-cryptography python-certifi and python-requests. Please consider adding those to the dependencies.

bluehood commented on 2019-06-14 09:51 (UTC)

Cannot install package due to a breakage in libarcus-git -- also reported to the proper page.

ad1217 commented on 2018-02-14 18:10 (UTC) (edited on 2020-03-01 18:53 (UTC) by ad1217)

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.

GPereira commented on 2018-02-14 16:07 (UTC)

Please update the version number regularly, or orphan it. The idea of this packages is to always have the latest versions @ad1217

ad1217 commented on 2018-02-13 23:11 (UTC)

@GPereira: I've bumped the version numbers for this and related packages ({cura-fdm-materials,cura-binary-data,curaengine,libarcus,uranium,cura}-git), but they are git packages, and were still building/running properly. They don't need to be updated constantly.

ad1217 commented on 2017-10-19 07:46 (UTC) (edited on 2017-11-08 05:34 (UTC) by ad1217)

@bpietras Seems to be a known issue: https://github.com/Ultimaker/Cura/issues/2596. Workaround is to either downgrade QT or use the AppImage for now. Edit: Seems to be fixed

bpietras commented on 2017-10-13 08:30 (UTC)

A qt update seems to have broken this. After updating both cura-git & uranium, the package makes without issue. QMake version 3.1 Using Qt version 5.9.2 in /usr/lib cura [...] 2017-10-13 09:25:08,875 - DEBUG - UM.Qt.Bindings.Theme.load [231]: Loaded theme /usr/share/cura/resources/themes/cura-light 2017-10-13 09:25:19,249 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles [hung]

ad1217 commented on 2017-09-21 16:12 (UTC)

@foxxy Thanks for mentioning it. They finally fixed it upstream, so I've now removed the patch.

foxxy commented on 2017-09-21 11:40 (UTC)

Hi, Failed apply the site-packages-dir.patch when building this morning. Thanks for the package.

ad1217 commented on 2017-09-14 06:53 (UTC)

@jvybihal errr, it is? (uranium-git?) Not sure how you didn't have it installed.

jvybihal commented on 2017-09-14 06:52 (UTC) (edited on 2017-09-14 06:54 (UTC) by jvybihal)

@ad1217 thanks, I did not even had uranuim installed before. By installing it, it builds. Maybe you should add it as dependency ;) edit: sorry, I see it is a dependency, no idea why yaourt did not install it then :/

ad1217 commented on 2017-09-11 14:48 (UTC)

@jvybihal your Uranium is out of date. I've just bumped a bunch of packages' versions up, updating them should fix it.

jvybihal commented on 2017-09-11 10:55 (UTC)

Failing to build. ==> Starting build()... CMake Error at CMakeLists.txt:30 (include): include could not find load file: UraniumTranslationTools CMake Error at CMakeLists.txt:34 (CREATE_TRANSLATION_TARGETS): Unknown CMake command "CREATE_TRANSLATION_TARGETS". -- Configuring incomplete, errors occurred! See also "/tmp/yaourt-tmp-jv/aur-cura-git/src/Cura/build/CMakeFiles/CMakeOutput.log". CMakeOutput.log: The system is: Linux - 4.12.10-1-ARCH - x86_64

ad1217 commented on 2017-02-07 21:23 (UTC)

I believe this is somewhat of a known bug: see https://aur.archlinux.org/packages/cura/ and https://github.com/Ultimaker/Cura/issues/1072 for discussion. Current workaround is to use the AppImage version of Cura. Alternatively, wait for a fix upstream.

doragasu commented on 2017-02-07 20:56 (UTC)

I have rebuilt everything and it now segfaults in libQt5Gui: python3[30399]: segfault at 10000001f ip 00007fd7547f1e39 sp 00007ffdb4b8c470 error 4 in libQt5Gui.so.5.8.0[7fd7546f2000+522000]

doragasu commented on 2017-02-07 19:55 (UTC) (edited on 2017-02-07 19:57 (UTC) by doragasu)

It segfaults on my machine :( python3[15987]: segfault at 100000341 ip 00007f503d0ea446 sp 00007fff0f93c3d8 error 4 in libc-2.24.so[7f503d06a000+195000] Any suggestions?

ad1217 commented on 2016-08-19 15:54 (UTC)

doragasu: Added (to uranium-git), thanks!

doragasu commented on 2016-08-19 10:17 (UTC)

PKGBUILD is missing required python-scipy dependency (maybe it should be an uranium dependency, I'm not sure).

bartus commented on 2016-03-17 19:00 (UTC) (edited on 2016-03-17 19:16 (UTC) by bartus)

Package won't build: PKGBUILD and site-packages-dir.patch needs update. PKGBUILD: chmod and symlinking aren't needed any more. site-packages-dir.patch: need to be updated against new formatting in CMakeList.txt

Frans-Willem commented on 2016-02-21 21:45 (UTC)

Yes, compiles again, thank you :)

ad1217 commented on 2016-02-15 15:36 (UTC)

Should work now. They keep changing CMakeLists, and their linux code is written for Ubuntu/Debian (dist-packages instead of site-packages).

Frans-Willem commented on 2016-02-15 15:07 (UTC)

No longer compiles, the patch to CMakeLists.txt is rejected :/

ad1217 commented on 2015-08-24 04:00 (UTC)

@greyltc: Annnnnd with a bit more research, that seems to be an upstream issue: https://github.com/Ultimaker/Cura/issues/277. I'll try to work on it more tomorrow. Also, I don't think python-power-git is required anymore. I removed it and python-opengl (which also doesn't seem to be necessary anymore).

ad1217 commented on 2015-08-24 03:49 (UTC)

@greyltc: I uploaded what I have. With this, it launches, gets to the machine selection window, but crashes right after. I have not yet been able to fix this.

ad1217 commented on 2015-08-23 16:38 (UTC)

@greyltc: They changed some of their packaging recently, and I have been working on fixing this package to match. I hadn't uploaded anything yet since I didn't think that anyone was using it (and it doesn't quite work yet). I'll upload what I have tonight.

greyltc commented on 2015-08-23 16:30 (UTC)

The cura app can not find the resources provided by Uranium. I'm not sure what the proper workaround for that is.

greyltc commented on 2015-08-23 16:14 (UTC)

The Arcus python module (from the libarcus-git package) is somehow installed in a different and still incorrect location. The workaround for launching the app which includes solving that problem then becomes: PYTHONPATH=$PYTHONPATH:/usr/lib/python3/dist-packages/:/usr/local/lib/python3/dist-packages cura_app.py

greyltc commented on 2015-08-23 15:52 (UTC)

This package isn't putting the python modules where Arch expects. The issue I mentioned in my previous comment can be worked around by launching the app like this: PYTHONPATH=/usr/lib/python3/dist-packages/ cura_app.py

greyltc commented on 2015-08-23 15:46 (UTC)

After fixing a few minor issues with the PKGBUILD, the package builds. However when I try to run the app: $ cura_app.py Error in sys.excepthook: Traceback (most recent call last): File "<frozen importlib._bootstrap>", line 2237, in _find_and_load File "<frozen importlib._bootstrap>", line 2212, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed ImportError: No module named 'cura' Original exception was: Traceback (most recent call last): File "/usr/bin/cura_app.py", line 14, in <module> import cura.CuraApplication ImportError: No module named 'cura'

greyltc commented on 2015-08-23 15:26 (UTC)

python-power-git does not exist