Cura
Cura copied to clipboard
Ultimaker
Cura Crashes When Uploading To Octoprint
Cura Version
5.7.0
Operating System
Windows 11
Printer
Creality Ender 3 S1 Pro
Reproduction steps
Sliced a file, tried to upload it to Octoprint
Actual results
Cura Shuts down a few seconds after rendering file for upload to Octoprint.
Expected results
File Should load successfully and prompt a link to Octoprint.
Add your .zip and screenshots here ⬇️
I have no screenshots to use because cura just closes.
Hi @NokEternal , thanks for the report ! This issue is quite annoying, but I fail to see a reason why Cura would crash right now. Did you run previous versions of Cura before ? It would greatly help us if you can provide your log files so that we can see what is happening. And by the way, Octoprint access is a Cura plugin that is not developped by us, so you may get more relevant help on the plugin page.
Hi @NokEternal , thanks for the report ! This issue is quite annoying, but I fail to see a reason why Cura would crash right now. Did you run previous versions of Cura before ? It would greatly help us if you can provide your log files so that we can see what is happening. And by the way, Octoprint access is a Cura plugin that is not developped by us, so you may get more relevant help on the plugin page.
I had to reread your comment a few times to get the gist of what you were asking for lol, anyhow I did look through all my folders and whilst I found how to get into said folders, I don't actually see any cura.log file to share with you, i see all other folders but no actual log, i will take a screenshot of this and maybe i'm just confused?
I don't actually see any cura.log file to share with you
Well I do see it on your screenshot :smiley: it is actually the "cura" file referenced as being a "Text Document". By default, Windows hides the files extension of common types (which is a nightmare), so in this case the file is indeed called "cura.log" by it will only display "cura".
I was actually able to find what I think would be the log after re-reading your reply, sorry for any delays on my behalf. Busy Busy.. Anyhow above should be the attached log file, Anymore help on this situation like I said would be greatly appreciated, and thank you again for your response as well as time on the issue. Hope to get it resolved quite shortly.
Just checked again and the problem is still persisting, It's with any file and like I said initially, Cura doesn't respond with any known error code or failure, it simply just closes out as soon as I click the "Print with Octoprint" button,.. Which is odd as I do believe 5.7 is the newest version out for cura, this didn't happen to me on 5.6 before the initial switch over..
Hi, and sorry for the delay. I took a deep look at your log file, but couldn't find anything relevant. I do see the application suddenly stopping to log, but no indication of why it would have crashed. I see you have already opened a new issue on the octoprint plugin page, hopefully they can help you more.
Hopefully in the next cura update this issue can be addressed.. Whilst annoying there is actually a work around that i've had to resort too, in order to keep printing with Cura, If anyone is having this same issue, the work around is quite simple. Slice said file in preferred settings and then "export g code" and then with octoprint upload file manually/locally and it seems to work fine then. Anyways i'll keep checking in occasionally with any if at all updates on this matter. thank you for those who have stayed persistent with this issue, as it really is rather annoying.
I'm afraid we (as Cura team) won't address this issue because this is related to the plugin. I hope @fieldOfView can help you on this. But I'm a bit puzzled because you seem to be using the plugin in the most standard way, and you have a very repeatable crash that is completely blocking. So we should see more people having the same issue, but maybe this is related to something in your specific environment. Have you tried the classic method of uninstall Cura - clear all configuration - reinstall Cura ?
I'm afraid we (as Cura team) won't address this issue because this is related to the plugin. I hope @fieldOfView can help you on this. But I'm a bit puzzled because you seem to be using the plugin in the most standard way, and you have a very repeatable crash that is completely blocking. So we should see more people having the same issue, but maybe this is related to something in your specific environment. Have you tried the classic method of uninstall Cura - clear all configuration - reinstall Cura ?
I actually have not, whilst I am familiar with uninstalling a program, I haven't done so as of yet but am down to give it a shot, just so i'm clear on this process, how would I go about clearing the entirety of the cura configuration contents to help assist with said dilemma??? I just want to make sure i'm thorough on these next few steps, so I can in fact see if it is something I'm perhaps doing wrong? anymore help on this situation is as always very appreciated. I just want to get back to printing without having to do any of the above said work around's and or possible bug that I am currently on hand with, Thank you so much again on this matter, I very much do appreciate any and all effort towards this issue..
I'm seeing the same crash issue when sending to OctoPrint since 5.7.0.
v5.6.0 works fine when sending the file.
I'm having the exact same problem since 5.7.0... It is NOT the plugin as it used to work fine.
I am floored that they are saying it MUST be YOUR environment because you are the only person to take the time to submit an issue... LAME AF!! It is Cura 5.7, not the environment.
Whilst it is nice to see others and me not being the only one in the entire world having this problem, it is also quite rather frustrating, The only work around I have found using Cura 5.7 was to export the g.code file after being sliced and then uploading it locally via the octoprint homescreen. It is rather annoying though not having that instant gratification, I do indeed hope the cura team can address this issue, as I am not the only one...
I am floored that they are saying it MUST be YOUR environment because you are the only person to take the time to submit an issue... LAME AF!! It is Cura 5.7, not the environment.
Well now we have three users having the same issue, we may consider that this is not the environment indeed, but in the first place we have to assume it, because it is a major root cause of issues.
It is rather annoying though not having that instant gratification, I do indeed hope the cura team can address this issue, as I am not the only one...
I agree that this is a very annoying issue. I will bring it for discussion with the team and see if we can spend some time on it, to at least try and find what is causing it.
I'm having the exact same problem since 5.7.0... It is NOT the plugin as it used to work fine.
Somehow the plugin may need an update because of the changes introduced in 5.7. So you are right, the plugin itself is not faulty indeed, but it is like "no more compatible" with the new version. We have a lot mechanisms in place to avoid those situations, but it is quite impossible to completely erase them.
FYI, we will be taking a look at this in the next sprint. For internal reference: CURA-11901