It is a fresh install on new 1Tb nvme ssd drive. Ubuntu server LTS latest version.
At this point I think I will start over and re-install everything and start with a single instance of Klipper after that.
This all started because I added a new Qidi Q1 Pro to my print farm a few weeks ago and switched to using Orca slicer for the Q1 Pro. I like Klipper and Orca and can see where I can stream line print starts and help with version control and replace the SD Card sneaker net.
OK, wiped hard drive, did fresh install Ubuntu server 24.04 LTS
Lenovo Tiny PC, AMD R7, 8Gb Ram, 1Tb nvme ssd.
Installed single instance Klipper, moonraker, and fluid using KIAUH
Exact same issue.
Researched a bit to find out how to downgrade newlib to 4.2 but couldnāt find how to do it. It seems other people are have the same problem but using different Linux flavor. so it seems I am stuck.
Since 24.04 is brand new, it is entirely possible that some updated packages contained breaking changes that now negatively impact Klipper.
The same was true for the upgrade to Debian Bookworm. Another example has been distros that suddenly shipped Python 3.12, which also brought breaking changes.
One option would be to use Debian Bookworm or if you want to use Ubuntu, then go back to 22.04.
Otherwise, you might have to wait until a developer looks at potential breaking changes.
Klipperās linker script does not contain any location for the exception table, which is required by newer versions of libnewlib. Iāve been running into this on Opensuse for quite some time. It also doesnāt define a heap, which some configurations donāt care about.
Iāve had success adding sections for the exception index, and a one byte heap.
This branch is stale, but it contains the same patchset. Iāve been using for 1y+.