Help fixing config errors due to klipper/moonraker/etc updates

[EricE555]

Printer Model

Voron 2.4

Extruder Type

Clockwork 2

Cooling Type

Stealthburner

I have been reunited with my printer after a 6 month separation. First thing I did after booting it was to update all the software to the latest versions (klipper/moonraker/etc). Now it won't boot and shows a "mcu 'mcu': Unable to connect" error. I can't make enough sense of the logs to know what to change. Any help is appreciated.
Edit: I should mention that it was working perfectly 6 months ago before I packed it away for moving.

Posting the klippy.log file and the printer.cfg.

 

[shiftingtech]

mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f446xx_1D0047000451303439343636-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f446xx_1D0047000451303439343636-if00'

probably the udev bug.

Klipper is broken, do not update until it is patched

I should have posted this a while ago but Klipper is broken, do not update you printer until it is fixed. This was pinned by ShiftingTech on the Voron Discord, A bug has been introduced in Debian Bullseye (which includes current MainsailOS), which prevents the symlinks in /dev/serial/by-id/...

forum.vorondesign.com

 

[EricE555]

mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f446xx_1D0047000451303439343636-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f446xx_1D0047000451303439343636-if00'

probably the udev bug.

Klipper is broken, do not update until it is patched

I should have posted this a while ago but Klipper is broken, do not update you printer until it is fixed. This was pinned by ShiftingTech on the Voron Discord, A bug has been introduced in Debian Bullseye (which includes current MainsailOS), which prevents the symlinks in /dev/serial/by-id/...

forum.vorondesign.com

Thank you for that. Very helpful. I'll see if I can take one of the actions listed to fix it. Much appreciated.
Edit: yep, that did the trick. I am back up and running. Thanks again.