What's new in v1.5.0
A mix of new reliability features and real bugs fixed — most of them found and confirmed on
actual printers, not just in testing.
⚠️ You need to re-run the full installer to get everything in this release — the in-app
"Update Guppy" button on its own is not enough. "Update Guppy" only refreshes the screen app
binary itself. The filament-change (M600) fixes and the new automatic disk cleanup both live
outside that — only the full installer applies them. See Upgrading below.
New: automatic disk cleanup
Old Klipper SAVE_CONFIG backups (created every time you calibrate something) used to pile up
forever — printers that had been calibrated many times over could have 100+ old backup files
sitting around, slowly eating storage. A small cleanup service now runs automatically at every
boot and keeps just the most recent one, no setup or action needed. It also clears old log files
and, only if you're critically low on space, old gcode files — never anything less than a week
old.
More reliable installs and updates
A batch of real installer bugs were found and fixed by testing repeatedly on a live printer:
- Updating could leave Mainsail/the web UI broken. An upgrade could clobber Mainsail's own
configuration, or skip a needed fix because of a faulty version check. The installer now
verifies and repairs this on every run, regardless of what version you're coming from. - The installer now refuses to start if you're critically low on storage, instead of
potentially failing partway through and leaving things half-done. - Downloads are now double-checked before anything is extracted, so a corrupted or interrupted
download can no longer sneak through and break your install.
Fixed: filament-change (M600) screen showing two dialogs at once
If your filament ran out (or a print called for a filament change), you could sometimes see two
overlapping "what do you want to do" dialogs stacked on top of each other — confusing, and easy
to tap the wrong button. This is fixed: you'll now always see exactly one dialog.
Two smaller bugs in the same area, also fixed:
- Tapping Cancel Print on that dialog could cancel the print correctly but leave the dialog
itself stuck on screen afterward. - The Resume button on that dialog was always blue, even if you'd picked a different theme
color in Settings — it now matches whatever theme you're using.
Fixed: a rare crash when cancelling right after a filament runout
Cancelling a print could, in one specific circumstance, drive the bed into the back of the
printer hard enough to lose steps — the same class of bug fixed for the regular Pause/Resume
button in an earlier release, just a separate copy of the same unsafe park position that only
Cancel Print used. Both are now fixed.
Fixed: adaptive bed mesh could silently fall back to a full-bed mesh
If your slicer's start G-code still had a leftover BED_MESH_PROFILE LOAD=default line (common
if you migrated from an older KAMP-based setup), it could quietly reload the full-bed mesh right
after the faster adaptive one finished calibrating — with no error, so you'd never know it
happened. If you have that line in your custom start G-code, remove it; see
Adaptive Print Setup.
Upgrading
sh -c "$(wget --no-check-certificate -qO - https://raw.githubusercontent.com/coreflake1/guppyscreen/main/scripts/installer.sh)"Full Changelog: v1.4.2-OpenKE...v1.5.0-OpenKE