-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ultimaker Cura 4.5 Issues #7372
Comments
Thanks for the report. If you're getting the welcome flow at each startup, that would indicate your user data isn't getting saved. You didn't specify if you're on Windows but I'm assuming you are. Try this:
Does it start cleanly? Does the welcome-flow-at-every-startup behaviour persist? If you want to restore your backed up files, simply drop each folder back in this location. Some relevant log output is here:
|
I am on Windows 10. And just do be clear, under AppData\Roaming\cura\ I have 3 folders (4.3, 4.4, and 4.5). Are these the configuration folders you are talking about? If so, I should probably delete the oldest ones (4.3)? And I guess my previous version was 4.4, not 4.4.1.
Chuck
Charles Totten
Operations Analyst
Sonalysts, Inc.
(860) 326-3810
|
I zipped my configuration folders for all 3 installations on the machine (4.3, 4.4, and 4.5). I then deleted those folders and opened Cura. I went through the Welcome screen process (expected), and set up a print file. All worked as expected. I closed Cura and reopened it. I did not get the Welcome screen this time, or the corrupt profiles warning. I set up another print file and sent it to the printers. I closed Cura again, and reopened without seeing the Welcome screen or the corrupt profile warning.
I think this fixed the problem. Thanks for the help.
In the future, when I upgrade to a newer version of Cura, should I make a point of deleting old configuration files?
Regards,
Chuck
|
This is more of a workaround than a fix, but glad to hear its got you in a position where you can use it again.
You shouldn't need to do this at all, there are scripts in place that are supposed to carry over your settings from a previous installation. We just did this to verify if there was an issue with your user settings, which seems to be the case. Have you installed any machine definitions or plugins manually? (i.e. by dragging and dropping files into your installation) Something in there is incompatible, but I'm not sure what. Perhaps someone else reading this has ideas. |
I have not installed any plugins. I am not sure what you mean by machine definitions. If you are referring to the printers installed, I have had some issues with that, mainly when I have to cycle power to a machine, since that changes to the IP address (since Ultimaker still has not provided for fixed IP addresses).
Charles Totten
Operations Analyst
Sonalysts, Inc.
(860) 326-3810
|
Hopefully this should (at least for part of the cases) be fixed for the upcoming 4.6, see commit 3c50b78 I'll close this as resolved for now, please open a new issue if this persists in the future new version. |
I installed Cura 4.5 about 3 weeks ago (previously was using Cura 4.4.1). Since the new installation, I have been having some odd issues.

Everytime I open Cura, it seems to think it is the first time I have opened it. I get the "Welcome" screen, where I have to agree to the Terms and Conditions, and it goes through the setup process, including adding networked printers.
Once I get into Cura, I keep getting a message saying my configuration is corrupt (see screen shot attached).
I went through the reset process that it recommended, and it seemed to work OK for a day or so, then it went back to the same issues. Cura log attached below.
cura.log
I have an Ultimaker S5 and 3E connected via ethernet. The printers seem to be working just fine, printing items from the Cura Connect queue, but the something definitely does not seem right with Cura. The welcome screen is annoying, especially when you see it daily. And I am tired of having to restore my tuned settings.
The text was updated successfully, but these errors were encountered: