Description of problem: I have no idea what caused this. Running from terminal gives this: File "/usr/bin/cura", line 27, in <module> from cura.CrashHandler import CrashHandler File "/usr/lib/python3.10/site-packages/cura/CrashHandler.py", line 27, in <module> from UM.Application import Application File "/usr/lib/python3.10/site-packages/UM/Application.py", line 9, in <module> from UM.Controller import Controller File "/usr/lib/python3.10/site-packages/UM/Controller.py", line 3, in <module> from UM.Scene.Iterator.DepthFirstIterator import DepthFirstIterator File "/usr/lib/python3.10/site-packages/UM/Scene/Iterator/DepthFirstIterator.py", line 3, in <module> from UM.Scene.SceneNode import SceneNode File "/usr/lib/python3.10/site-packages/UM/Scene/SceneNode.py", line 14, in <module> from UM.Mesh.MeshBuilder import MeshBuilder File "/usr/lib/python3.10/site-packages/UM/Mesh/MeshBuilder.py", line 4, in <module> from UM.Mesh.MeshData import MeshData File "/usr/lib/python3.10/site-packages/UM/Mesh/MeshData.py", line 16, in <module> import scipy.spatial File "/usr/lib64/python3.10/site-packages/scipy/spatial/__init__.py", line 102, in <module> from ._kdtree import * File "/usr/lib64/python3.10/site-packages/scipy/spatial/_kdtree.py", line 5, in <module> from ._ckdtree import cKDTree, cKDTreeNode File "_ckdtree.pyx", line 1, in init scipy.spatial._ckdtree ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject Running fedora 36 with 5.18.16-200.fc36.x86_64 kernel Nvidia graphics Cura version: 1:4.13.1-2.fc36 Version-Release number of selected component: cura-1:4.13.1-2.fc36 Additional info: reporter: libreport-2.17.1 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-glib-com.ultimaker.cura-10194.scope cmdline: /usr/bin/python3 /usr/bin/cura /home/jonathan/Downloads/labyrinthGiftBox_bottom.STL crash_function: init scipy.spatial._ckdtree exception_type: ValueError executable: /usr/bin/cura interpreter: python3-3.10.6-1.fc36.x86_64 kernel: 5.18.16-200.fc36.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: _ckdtree.pyx:1:init scipy.spatial._ckdtree:ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject Traceback (most recent call last): File "/usr/bin/cura", line 27, in <module> from cura.CrashHandler import CrashHandler File "/usr/lib/python3.10/site-packages/cura/CrashHandler.py", line 27, in <module> from UM.Application import Application File "/usr/lib/python3.10/site-packages/UM/Application.py", line 9, in <module> from UM.Controller import Controller File "/usr/lib/python3.10/site-packages/UM/Controller.py", line 3, in <module> from UM.Scene.Iterator.DepthFirstIterator import DepthFirstIterator File "/usr/lib/python3.10/site-packages/UM/Scene/Iterator/DepthFirstIterator.py", line 3, in <module> from UM.Scene.SceneNode import SceneNode File "/usr/lib/python3.10/site-packages/UM/Scene/SceneNode.py", line 14, in <module> from UM.Mesh.MeshBuilder import MeshBuilder File "/usr/lib/python3.10/site-packages/UM/Mesh/MeshBuilder.py", line 4, in <module> from UM.Mesh.MeshData import MeshData File "/usr/lib/python3.10/site-packages/UM/Mesh/MeshData.py", line 16, in <module> import scipy.spatial File "/usr/lib64/python3.10/site-packages/scipy/spatial/__init__.py", line 102, in <module> from ._kdtree import * File "/usr/lib64/python3.10/site-packages/scipy/spatial/_kdtree.py", line 5, in <module> from ._ckdtree import cKDTree, cKDTreeNode File "_ckdtree.pyx", line 1, in init scipy.spatial._ckdtree ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject Local variables in innermost frame:
Created attachment 1905026 [details] File: backtrace
Created attachment 1905027 [details] File: cpuinfo
Created attachment 1905028 [details] File: environ
Created attachment 1905029 [details] File: mountinfo
Created attachment 1905030 [details] File: namespaces
Created attachment 1905031 [details] File: open_fds
Sorry, I can't reproduce this, does it still happen to you? Could you share the versions of numpy and scipy? $ rpm -q python3-numpy python3-scipy $ python3 -c 'import numpy, scipy; print(numpy.__version__, numpy.__file__); print(scipy.__version__, scipy.__file__)' Thanks.
Hi, yes cura still fails to launch with same error. [jonathan@blackbox]~% rpm -q python3-numpy python3-scipy python3-numpy-1.22.0-2.fc36.x86_64 python3-scipy-1.8.1-1.fc36.x86_64 [jonathan@blackbox]~% python3 -c 'import numpy, scipy; print(numpy.__version__, numpy.__file__); print(scipy.__version__, scipy.__file__)' 1.21.4 /home/jonathan/.local/lib/python3.10/site-packages/numpy/__init__.py 1.8.1 /usr/lib64/python3.10/site-packages/scipy/__init__.py Thanks alot!
> 1.21.4 /home/jonathan/.local/lib/python3.10/site-packages/numpy/__init__.py This sounds like you installed numpy with pip. Does this error happen if you move (backup) /home/jonathan/.local/lib/python3.10 somewhere else?
Yes, as Miro says, there is a mismatch between numpy version installed as rpm from Fedora repos and numpy version in ~/.local (installed probably by pip) that gets loaded.
Wow, yes that fixed it. Im assuming that i should just move back the folder and uninstall numpy with pip?
That should do the trick.
Does it help if you move back the folder and execute cura this way? python3 -s /usr/bin/cura If so, I should probably modify /usr/bin/cura to include the -s flag.
Yes adding the -s flag makes it work even with numpy install with pip
Thank you so much for helping me. And for helping the entire Linux community.
https://src.fedoraproject.org/rpms/cura/pull-request/16 https://src.fedoraproject.org/rpms/cura/pull-request/17 https://src.fedoraproject.org/rpms/cura/pull-request/18 https://src.fedoraproject.org/rpms/cura/pull-request/19
FEDORA-2022-d0aac6952b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0aac6952b
FEDORA-2022-d0aac6952b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-80e848340d has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-80e848340d
FEDORA-2022-80e848340d has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-b28aa88b8f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b28aa88b8f
FEDORA-2022-59e178614f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-59e178614f
FEDORA-2022-b28aa88b8f has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b28aa88b8f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b28aa88b8f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-59e178614f has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-59e178614f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-59e178614f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-59e178614f has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-b28aa88b8f has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.