Cura will not open up

[a7abw 0]

I've been using V5.4 and 5.5 without any issues until yesterday - but clicking on the Cura icon now does not open the program. I downloaded and installed V5.6 but have the same result.

 

I'm running Windows 10 and haven't changed anything on my computer (at least not to my knowledge).

 

Any advice / recommendations will be appreciated.

 

Thank you.

[Slashee_the_Cow 443]

If you could post the cura.log file from %APPDATA%\cura\5.6\ (as well as 5.5 and 5.4 if they were working fine) and if it's there, the stderr.log file from %APPDATA%\cura\ we can have a look to see if anything looks amiss.

[a7abw 0]

Good morning Slashee, thank you for the response.

 

There is no cura.log in the 5.6 folder, only a cura.cfg file.

The 5.5 folder only has a cura.log.1 file

The 5.4 folder only has a cura.cfg file

There are no stderr.log files in any of the folders

Earlier versions (all the way back to 4.8) all contain the cura.log.1 files

 

I tried to attach the cura.log.1 file from 5.5 but it gets rejected.

 

I hope that this helps you to diagnose the problem.

 

Thank you

[DivingDuck 105]

Make a backup of all the %APPDATA%\cura\x.x\  folders and then delete all of the x.x folders. This sometimes helps to get Cura to the point initializing itself w/o trying to integrate former configuration files. Maybe it help you too. You can then try later adding the old configurations back from your backup and check where the problem came from.

 

Regarding not able to attach the log file. Make a zip file from  the log file and attach the zip. This should work.

Edited March 9 by DivingDuck
Edit info for attaching a log file here

[Slashee_the_Cow 443]

3 hours ago, DivingDuck said:

Make a backup of all the %APPDATA%\cura\x.x\  folders and then delete all of the x.x folders.

Skip the middleman. Rename the entire cura folder.

[a7abw 0]

Thanks DD, but that file has a .1 after cura.log.1 Not sure if this can cause some issues.

 

Slashee, please elaborate a bit, I'm not not very clear on your suggestion.

I assume you are referring to the main cura folder in AppData/Roaming/cura)?

What do I do after renaming the folder? Please excuse my ignorance.

Thanks.

[a7abw 0]

Slashee, I did rename the folder as cura.test and when I launched Cura, it recreated cura as a new folder and the program opened normally. However, none of my previously saved profiles are there - is it possible to retrieve them from the cura.test folder?

Thank you for your continued input.

[DivingDuck 105]

47 minutes ago, a7abw said:

Thanks DD, but that file has a .1 after cura.log.1 Not sure if this can cause some issues.

Guess you tried to zip the log file and somehow the file extension was overwritten with .1

 

16 minutes ago, a7abw said:

However, none of my previously saved profiles are there - is it possible to retrieve them from the cura.test folder?

Yes, you can copy the profiles from your renamed folder. and look if Cura will start. If Cura wont start after copying the files you can delete them again and add a new printer profile as you did that the first time using Cura.

Up to this point we now already that Cura will start again if you remove the old configuration folder. This is already progress. +1

 

When you try to copy the old configuration please do not copy the plugin folder. This way you can check if the problem came from an older plugin version.

Edited March 9 by DivingDuck

[JRRead07 0]

This is so odd.  I was on 5.7.1 ever since it came out.  I have been running prints every day for the last week on a project with no issues.  This week, while I was loading a gcode file, it closed suddenly.  I now try to open and the disc icon just spins then disappears with no Cura running, no minimized, not in "services", nowhere.  I tried everything listed above in this post with no success. Attached is everything from the 5.7 folder.  I tried 5.7.2 with no success.  Uninstalled all versions, re-boot each time.  Re-installed 5.7.2, re-boot, no success.  Uninstalled that one, re-boot.  Re-installed previous working one that crashed, 5.7.1., re-boot, no success.  I will try one last uninstall, re-boot, and install the new beta.....?  I don't see that any windows update (I am on an Acer PC with Win10) that were installed in the last couple days, but will uninstall everything that was updated this week and see if that affects anything.

5.7.zip

[Slashee_the_Cow 443]

@JRRead07 Is there no cura.log file? Because if there is, posting that would really help (just a config folder isn't too much to go by). Also go to %APPDATA%\cura\ and see if there are files called STDOUT.log or STDERR.log and post them.

 

Try going to %APPDATA%\ and rename the cura folder to cura.old or something then run Cura. It should start from fresh, so you'd have to set stuff up again, but then at least you've narrowed down the problem to something in the config folder. You can copy over things like quality profiles from the old folder, but only do one sort of thing at a time, and then if it stops working, you've found your culprit.

[JRRead07 0]

Both those files - stdout andstderr are blank.  I already tried the renaming, though I re-named it .tst.  It is odd that I changed nothing.  I simply was loading a previously used gcode file.  I had printed it, then printed something else, then tried loading the first one.  Crapped out and has not worked all day today.

cura.zip

Edited July 17 by JRRead07
adding files....or trying to.

[Slashee_the_Cow 443]

4 hours ago, JRRead07 said:

It is odd that I changed nothing.  I simply was loading a previously used gcode file.  I had printed it, then printed something else, then tried loading the first one.  Crapped out and has not worked all day today.

You know, you don't have to attach blank files to a post. I believe you 🙂

 

Unfortunately while I believe you, I'm not sure there's much I can do to help you. Cura shouldn't have anything persistent other than the configuration folder so between rebooting and getting it to generate a new config folder that should remove anything that might have killed it.

 

I think that until someone else on the forum comes up with some obvious solution I didn't think of, you should probably submit a bug report. Make sure to include the gcode file that killed it and all the troubleshooting steps you already tried.

[JRRead07 0]

Thank you StC. I did get a bunch of "AppCrash_UltiMaker-Cura.e_" files with a big string of charachters after it.  It is a ".wer" file and not sure how to open it.  I also found some "crash dump" files - attached.

CrashDumps.zip

Edited July 18 by JRRead07

[Slashee_the_Cow 443]

I'm pretty sure .wer files are Windows Error Reporting. Other than that I wouldn't have the first clue what to do with them 😞

 

If you put a bug report in on the Cura GitHub, you should go attach those .wer files and the crash dumps. If you didn't put in a bug report... you really should, because it's a direct line to people who know a lot more than me about the internals of Cura 🙂 

[JRRead07 0]

I ended up doing a system restore point a couple saves up....back to July 01 just to be safe.  One re-boot later, install fresh 5.7.2 on C:\UltiMaker Cura 5.7.2 and viola....working great.  It must have been one of the various Win updates or driver updates from "Intel Driver and Support Assistant".  I saw that did an update recently as well.  All seems ok at the moment, but have not re-booted a second time until I get my 3 prints completed.

[Slashee_the_Cow 443]

32 minutes ago, JRRead07 said:

All seems ok at the moment, but have not re-booted a second time until I get my 3 prints completed.

Great to hear you got it working, but please tell me you're not printing over USB - this is a very good reason why, if a memory card stuck into your printer fails when your computer reboots that would be a pretty impressive achievement.