Your message dated Tue, 12 Aug 2025 18:34:19 +0800
with message-id <[email protected]>
and subject line Upstream bug is closed, closing this too
has caused the Debian Bug report #1061065,
regarding Impossible to use Gcode produced in prusa on Ender 3 S1 Pro
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1061065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061065
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: prusa-slicer
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.
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-17-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages prusa-slicer depends on:
ii fonts-noto-hinted 20201225-1
ii libboost-chrono1.74.0 1.74.0+ds1-21
ii libboost-filesystem1.74.0 1.74.0+ds1-21
ii libboost-iostreams1.74.0 1.74.0+ds1-21
ii libboost-locale1.74.0 1.74.0+ds1-21
ii libboost-log1.74.0 1.74.0+ds1-21
ii libboost-regex1.74.0 [libboost-regex1.74.0-icu72] 1.74.0+ds1-21
ii libboost-thread1.74.0 1.74.0+ds1-21
ii libc6 2.36-9+deb12u3
ii libcurl3-gnutls 7.88.1-10+deb12u5
ii libdbus-1-3 1.14.10-1~deb12u1
ii libexpat1 2.5.0-1
ii libgcc-s1 12.2.0-14
ii libgl1 1.6.0-1
ii libglew2.2 2.2.0-4+b1
ii libglib2.0-0 2.74.6-2
ii libgmp10 2:6.2.1+dfsg1-1.1
ii libgtk-3-0 3.24.38-2~deb12u1
ii libimath-3-1-29 3.1.6-1
ii libjpeg62-turbo 1:2.1.5-2
ii libmpfr6 4.2.0-1
ii libnlopt0 2.7.1-5
ii libocct-data-exchange-7.6 7.6.3+dfsg1-7
ii libocct-foundation-7.6 7.6.3+dfsg1-7
ii libocct-modeling-algorithms-7.6 7.6.3+dfsg1-7
ii libocct-modeling-data-7.6 7.6.3+dfsg1-7
ii libocct-ocaf-7.6 7.6.3+dfsg1-7
ii libopenvdb10.0 10.0.1-2
ii libpng16-16 1.6.39-2
ii libstdc++6 12.2.0-14
ii libtbb12 2021.8.0-2
ii libwxbase3.2-1 3.2.2+dfsg-2
ii libwxgtk-gl3.2-1 3.2.2+dfsg-2
ii libwxgtk3.2-1 3.2.2+dfsg-2
prusa-slicer recommends no packages.
prusa-slicer suggests no packages.
-- no debconf information
Thank you for using reportbug
--- End Message ---
--- Begin Message ---
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.
--
Kind regards,
Loong Jin
signature.asc
Description: PGP signature
--- End Message ---
