My printer is in the middle of a rebuild and all the cables are lying around, I've even terminated some new ones (like the 3DTouch to remove the Dupont connectors and use proper JST-XH) and made extensions (Z stepper and Y endstop).
Contrary to what the name bugfix might imply, that's actually a development branch and build you have running there. So yes, I strongly suggest trying a stable release version instead.
FAQ for that:
From your logs:
2024-07-03 11:26:03,437 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2024-07-03 11:26:04,518 - octoprint.util.comm - ERROR - Unexpected error while reading from serial port
Traceback (most recent call last):
File "/home/pi/oprint/lib/python3.9/site-packages/octoprint/util/comm.py", line 4172, in _readline
ret = self._serial.readline()
File "/home/pi/oprint/lib/python3.9/site-packages/octoprint/util/comm.py", line 6931, in readline
c = self.read(1)
File "/home/pi/oprint/lib/python3.9/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2024-07-03 11:26:04,630 - octoprint.util.comm - ERROR - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
I did go back to 2.0.x and also had a serial disconnection. In the logs I saw that it was related to MeatPack so I disabled it. Did some dry runs first and some actual test prints later and everything turned out fine. The quality was pretty good too!
So I'm positive this can be resolved. Maybe in the future I'll try 2.1.x again now that I know what to look for.