Version: 2.5.0+dfsg-4


When producing a Gcode on prusa-slicer 2.5.0+dfsg-4, the Ender 3 S1 Pro
cannot read it.

The problem is inherent to prusa-slicer, as showed int this bugreport on
the github repo (https://github.com/prusa3d/PrusaSlicer/issues/8883)

I suggest to update the stable release of prusa-slicer.

tags 1061065 + upstream fixed-upstream
forwarded 1061065 https://github.com/prusa3d/PrusaSlicer/issues/8883

Looks like the upstream bug has been fixed, and Debian's on the latest
version of Prusa Slicer so I'm assuming this is fixed too.

This bug doesn't have enough information to conclude whether it's the
same bug or not, but generated gcodes not working with a specific
printer is usually a config issue, and there seems to be a config bundle
that PrusaSlicer downloads from their servers that fixes it.