configuration Get error on Cura startup: "Your configuration seems to be corrupt"

[Bluescreen2001 0]

Hi
I just installed the "printer settings" plugin from the marketplace to my Cura 5.1 installation. After that I cannot start Cura anymore because of the following error message:

 

Quote

 

Your configuration seems to be corrupt. Something seems to be wrong with the following profiles:
- Voron #2

Would you like to reset to factory defaults? Reset will remove all your current printers and profile.

 

 

No, I don't want to reset all my settings! So I quit Cura without doing anything else.
I spend days for optimising and calibrating my settings. What can I do to solve that issue. I attach the Cura log to this message and hope someone can help me.

 

Then mentioned Voron #2 profile was an early experiment to add a second (virtual) extruder. But this was there for ages and not used. If it is possible to remove this, mthat maybe a solution.

cura.log

 

[Slashee_the_Cow 274]

If you just remove the the definition file for Voron #2 (looks to be called voron2_300), that should fix it. The error shouldn't affect other machines anyway, but it is a bit annoying. Ideally (it depends where you put it), your definition for Voron #2 is in the Cura configuration folder. In Cura, go to Help > Show Configuration Folder and look in the definitions folder.

 

If you saved it in the same folder as all the included definitions, by default (in Windows) that will be C:\Program Files\UltiMaker Cura 5.1.0\share\cura\resources\definitions\

 

If you created a custom extruder file for it, you'll also need to delete that from the extruders folder (in whichever location you ended up saving it).

[Bluescreen2001 0]

Hi Slashee

 

Thank you for your answer. First, I cannot go to Show Configuration folder because I cannot start Cura without loosing my settings.
I find the file named voron2_300.def.json in folder C:\Program Files\Ultimaker Cura 5.1.0\share\cura\resources\definitions. But this has an old modification date, which fits the installation date of Cura. So I don't think, this is the cause. I tried to remove it without success.
The only new file there is voron2_base.def.json. I don't know, why it has a newer modification date. I attach it here.

It seems to reference an extruder file named voron2_extruder_0 which also has an old modification date. I attach it, too.

Strange is also that I now get two corrupt profiles: Voron and Voron_user. No Voron #2 anymore.

 

The only way to start Cura is to delete the folder C:\Users\<username>\AppData\Roaming\cura. But then I loose all my settings.

But what do I really loose this way? The printer settings itself is no great deal, because it's a standard Voron. But what about materials and some calibration settings like flow or something. Are these included my 3mf files of old jobs? For me it is very unclear where Cura stores which data. It would be much easier if there would be different file save/load options for things like materials, machine parameters, print profiles because then it would be clear. Now I never know where which parameters come from. So I always load an old project, delete all objects and insert the new ones.

 

voron2_base.def.json.log voron2_extruder_0.def.json.log

[GregValiant 1,260]

DON'T RESET.

The "Do you want to reset" box has an "X" in the top right corner.  Use it to dismiss the warning box.  Cura will start and you can delete the offending printer or do what you need to do without starting from scratch.  Eventually you will find the corrupt file and Cura will start without the warning.

If a corrupt/wrong temporary setting file exists in the AppData/Roaming folder then Cura can balk at starting.  Which file it is becomes the question.  It might be a definition file, nozzle file, or extruder file.

Edited November 16, 2023 by GregValiant

[Bluescreen2001 0]

Yes, I did this (closing with X). Then Cura starts with it's initial setup process (select printer, etc.). I closed that too, because I thought it will overwrite my settings then.

Edited November 16, 2023 by Bluescreen2001

[GregValiant 1,260]

The "Voron2 base" definition you posted is a LOT different than the one I show in Cura.  Right off the bat - the version number is the second line and it should be the first line.  Cura notices things like that.  A single type and you get the "reset" warning as the file won't load.

There are a lot of changes to the overrides section including the formatting and addition of spaces/tabs.  That can be problematic if spaces and tabs are mixed on the same line.

Your file:

   "overrides":
    {
        "machine_name":                                 { "default_value": "VORON2" },
        "machine_width":                                { "default_value": 250 },

 

Stock file:

    "overrides":
    {
        "acceleration_enabled": { "default_value": false },
        "acceleration_layer_0": { "value": 1800 },

 

Here is the stock Voron2 Base file from my 5.5 installation.  

 

 

voron2_base.def.json.log

[Bluescreen2001 0]

It seems most of these changes are between 5.5 and 5.1. I checked the file on my 5.5 version of my companies laptop and compared it with yours. It's the same. I tried that file in my 5.1 installation and it doesn't change anything. I also checked my file for special characters like tabs. There are none. I also cannot really believe that spaces or tabs can break such file. It is JSON format and since most of Cura seems to be written in Python, I thing it uses standard json libs and they normally accept this. Missing comma, or brackets or something would break them, yes.

 

But what is interesting is ther version number. My Voron base file has version 2. Your's too. But the files in my AppData directory have version 4! I tried to change this for the voron2_extruder file there but it makes things worse. It the displays that file as incorrect, too.

 

I the searched for the string "Voron_user" in all files in all the Cura directories and don't find it. Where the hell ist that "user profile" located? Oh, that was stupid Windows find function. Good old grep find some locations.

 

I find one interesting thing in stderr.log:

stderr.log:2023-11-16 18:22:40,485 - ERROR - [MainThread] UM.Settings.ContainerStack.deserialize [429]: When trying to deserialize Voron, we received an unknown container ID (Voron_user)
stderr.log:2023-11-16 18:22:40,485 - ERROR - [MainThread] UM.Settings.ContainerRegistry.findContainers [217]: Exception: Error in the format of container Voron: When trying to deserialize Voron, we received an unknown container ID (Voron_user)

 

Containers are found in C:\Users\<user>\AppData\Roaming\cura\5.1\machine_instances/Voron.global.cfg. There you find a container Voron_user with number 0 and voron2_300 with number 7. But to what does this reference.

[Slashee_the_Cow 274]

5 hours ago, Bluescreen2001 said:

It is JSON format and since most of Cura seems to be written in Python, I thing it uses standard json libs and they normally accept this.

It isn't using the standard JSON libraries (or if it is, it isn't using them very well). Incorrect spacing (among other things) can, will and does break it. Not to mention that a lengthy string literal is a somewhat precarious way to hold JSON in the first place.

[pgramsey 0]

I want to chime in on this one.

 

The dialog "do you want to reset your configuration" is a very bad one.

 

First off, if one configuration is corrupt, don't offer to blow away the user's entire configuration set as the fundamental (and seemingly only) option. A user has to see the tiny, low contrasting "X" and realize that it is the way out of the problem.

 

Second, there is no simple way to delete the broken configuration. The "corrupt" configuration doesn't show up in the list of printers, so even after getting over the first hurdle there is no obvious way to get rid of it and make Cura happy again short of blowing away everything and starting from scratch.

 

This is a very user-unfriendly interface design.

 

[Slashee_the_Cow 274]

3 hours ago, pgramsey said:

I want to chime in on this one.

 

The dialog "do you want to reset your configuration" is a very bad one.

 

First off, if one configuration is corrupt, don't offer to blow away the user's entire configuration set as the fundamental (and seemingly only) option. A user has to see the tiny, low contrasting "X" and realize that it is the way out of the problem.

 

Second, there is no simple way to delete the broken configuration. The "corrupt" configuration doesn't show up in the list of printers, so even after getting over the first hurdle there is no obvious way to get rid of it and make Cura happy again short of blowing away everything and starting from scratch.

 

This is a very user-unfriendly interface design.

 

If you can elucidate ways in which it can be improved, then submit a feature request on the Cura GitHub repo.

[ahoeben 1,951]

I have only skimmed the discussion in this thread, but you could try installing the "Startup Optimiser" plugin from the Marketplace. It adds a button to the "Your configuration seems to be corrupt." dialog that lets you disable just that broken Voron 2 configuration file, and leave the rest intact.