New release: 1.6.1

This first bugfix release for 1.6.x fixes two bugs discovered in 1.6.0 after its stable release, one in the GCode viewer and one in the handling of SD file list requests during and ongoing print:

  • #4115 - GCode viewer: Fix dragging when a printer profile with center origin is selected. As a welcome side effect, this now also means the GCode viewer will finally update the bed dimensions properly on printer profile change.
  • #4119 - Fix blocking timeout when requesting an SD file list while printing & prevent an SD list refresh while printing.

You can also take a look at the short changelog on GitHub.

Like every single release (and release candidate) of OctoPrint ever since early 2016 this release was made possible only through your continued support of my work 💕


The heads-ups from 1.6.0 still apply, please read them carefully, they might impact you and how you use OctoPrint! Also see the Further Information and Links below for more information, where to find help and how to roll back.


Thanks to everyone who contributed to this bugfix release and provided full, analyzable bug reports, suggestions and feedback!

Further Information

It may take up to 24h for your update notification to pop up, so don't be alarmed if it doesn't show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.

If you get an error about "no suitable distribution" during update, please read this.

If you have any problems with your OctoPrint installation, please seek support on the community forum.


This is a companion discussion topic for the original entry at

:+1: well done

1 Like

I just installed 1.6.0 from img, once it was up and running I setup Octodash, then octoprint wanted me to install 1.6.1, I did now and now it will not start, and no logfile is created.


it appears occtoprint binary is zero bytes. I tried to do a pip and install latest and that didnt work either

I managed to do a force install with pip no idea what happened with the upgrade from 1.6.0 yo 1.6.1

Yo Jim, I have the same issue. Must be a bad release

Unlikely, given to this is the first we've heard of it after 45,000 confirmed installs. If you want help fixing it, please open a new Get Help thread will all the requested details.

1 Like