New release candidate: 1.3.10rc2

This second RC of 1.3.10 fixes a couple of regressions observed with the first one and also adds some improvements of existing or newly added functionality that became apparent during testing of RC1:

  • #2872 - Fix Timeout when connecting to printer that doesn’t send start on connect
  • #2873 - Fix GCODE viewer no longer being able to load files.
  • #2876 - Fix semi functional UI when access control is disabled
  • #2879 - Fix favicon in Firefox
  • Anonymous Usage Tracking: More error resilience for the wizard to possibly work around issues observed with the first RC (for which sadly no information was provided to reproduce and analyse).
  • Anonymous Usage Tracking: Added elapsed time & reason of print failure to tracking (to be able to distinguish cancelled from errored out prints)
  • Anonymous Usage Tracking: Added undervoltage/overheat detection on Pis to tracking (to correlate print failures to power issues, see also #2878).
  • Printer Safety Plugin: Added Ender 3 stock firmware to detection
  • Softwareupdate: More resilience against invalid data in config
  • Added documentation for octoprint.util.commandline module

You can find the full changelog and release notes as usual on Github.

Special thanks to everyone who contributed to this release candidate, especially @tedder for his PR.

As the past RC has shown me that a lot of people appear to be unaware of this: Please do not install this RC if you expect a fully stable version. It is not a stable release, it is a release candidate: severe bugs can occur, and they can be bad enough that they make a manual downgrade to an earlier version necessary - maybe even from the command line.

You should be comfortable with and capable of possibly having to do this before installing an RC.

If you want to and can help test this release candidate, you can find information on how to switch to the “Maintenance RCs” release channel in this guide if not already done (also linked below).

Please provide feedback on this RC. For general feedback you can use this ticket on the tracker. The information that everything works fine for you is also valuable feedback 😄. For bug reports please follow “How to file a bug report” - I need logs and reproduction steps to fix issues, not just the information that something doesn’t work.


Depending on how the feedback for this release candidate turns out, I’ll either look into releasing 1.3.10 or fix any observed regressions and push out a new release candidate ASAP.


This is a companion discussion topic for the original entry at

You forgot to change the link to the new general feedback ticket to the one for RC2:

1 Like

Yep, I noticed myself and already took care of it - thanks!