Update 1.2.7 UpdateFix not working #1698

shawnkirsch opened this Issue Jan 10, 2017 · 4 comments


None yet

3 participants


What were you doing?

Followed instructions via https://github.com/foosel/OctoPrint/releases/tag/1.2.8

Tried all possible

What did you expect to happen?

Update to 1.2.8

What happened instead?

Same, stuck on 1.2.7

Branch & Commit or Version of OctoPrint

1.2.7 Master Branch

Printer model & used firmware incl. version

Printrbot Play

Browser and Version of Browser, Operating System running Browser

Safari 10.12.2

Link to octoprint.log


Link to contents of terminal tab or serial.log

Not needed


Hi @shawnkirsch,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-01-24 06:40 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.


I have reread all the info. I realize the wording in the manual switching of branches was worded weirdly. I have updated some logs here:



seriously a gitbot?!

foosel commented Jan 10, 2017

That's just a shot in the dark, but since in your second link it's complaining about not being able to clean up the install prior to install and the following setup call then fails too, please try fixing your permissions.

If that isn't it, a manual update might have to be performed.

seriously a gitbot?!

Yes. Running after log files, version numbers and the like for nearly every ticket all the time becomes old fast, as does continuously answering the same questions already answered in the FAQ :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment