Dear Maintainer,

When Launching Cura and Navigating to the Machine Settings Window (with a configured printer); both the build plate shape and G-code flavor options remains blank (no choice can be selected)

Removing a Printer and Re-Adding a Printer does not fix the issue described above

When using CURA 5.11 (App Image Build) (both the build plate and G-code
flavor have options)

I have included a screenshot of the missing information

[image: Screenshot From 2025-12-01 23-04-44.png]

Hi,
yes, the version 5.0.0-6 is not up-to-date for python3-numpy.

During click to Preview in Cura, never-ending slider slides and the following
error appears in the terminal:

    ValueError: The binary mode of fromstring is removed, use frombuffer instead

with a context:

  2026-02-20 21:31:49,148 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/lib/cura/plugins/SimulationView/simulationview_composite.shader]...
  2026-02-20 21:31:49,195 - DEBUG - [JobQueueWorker [3]] CuraEngineBackend.ProcessSlicedLayersJob.run [74]: Processing new layer for build plate 0...
  2026-02-20 21:31:49,280 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]: Exception: Job <CuraEngineBackend.ProcessSlicedLayersJob.ProcessSlicedLayersJob object at 0x7f779f15fa10> caused an exception on worker JobQueueWorker [3]
  2026-02-20 21:31:49,281 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]: Traceback (most recent call last):
  2026-02-20 21:31:49,281 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]:   File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 133, in run
  2026-02-20 21:31:49,282 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]:     job.run()
  2026-02-20 21:31:49,282 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]:     ~~~~~~~^^
  2026-02-20 21:31:49,282 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]:   File "/usr/lib/cura/plugins/CuraEngineBackend/ProcessSlicedLayersJob.py", line 143, in run
  2026-02-20 21:31:49,283 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]:     line_types = numpy.fromstring(polygon.line_type, dtype = "u1")  # Convert bytearray to numpy array
  2026-02-20 21:31:49,283 - ERROR - [JobQueueWorker [3]] UM.JobQueue.run [135]: ValueError: The binary mode of fromstring is removed, use frombuffer instead
  beginResetModel called on OutputDevicesModel(0x2c490720) without calling endResetModel first
  endResetModel called on OutputDevicesModel(0x2c490720) without calling beginResetModel first


Thanks and Best Regards

Hi Zito,

Upstream still has this line of code [1], so I suppose we'll need to fix it ourselves.

The deprecation happened in numpy 1.14, according to [2], but it hadn't generated ValueErrors up until 2.3.0 (see release notes [3]).

Can you confirm that this is really the same bug as reported by Arcademan?
If not, please file a separate bug report.

I'll forward the issue upstream and try to prepare a fix.

Thanks!

[1] https://github.com/Ultimaker/Cura/blob/main/plugins/CuraEngineBackend/ProcessSlicedLayersJob.py#L143
[2] https://numpy.org/doc/stable/reference/generated/numpy.fromstring.html
[3] https://numpy.org/doc/stable/release/2.3.0-notes.html#expired-deprecations

I've pushed a patch to Salsa, and also a fix for a similar issue in Uranium.

https://salsa.debian.org/3dprinting-team/uranium
https://salsa.debian.org/3dprinting-team/cura

Fixed packages should arrive soon-ish. If you're in a hurry, you can also build them yourself from the Salsa repos.

No, this is a different problem. I can see Machine Settings dialog. But
I'm running Unstable.

Ok, I will fill a separate bugreport for Unstable…

Thanks