search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
5.95k stars 2.04k forks source link

Cura Appimage not saving cura.cfg #10976

Open Blue-Beaker opened 2 years ago

Blue-Beaker commented 2 years ago

Application Version

4.12.0

Platform

KUbuntu 20.04

Printer

Creality Ender 3

Reproduction steps

1.Change some settings related to ~/.local/share/cura/4.12/cura.cfg, such as settings visualibility 2.Close cura and relaunch it.

Actual results

The file ~/.local/share/cura/4.12/cura.cfg remains unchanged, so does the related settings.

The log file says the configuration is saved,but it doesn't.

Expected results

The ~/.local/share/cura/4.12.0/cura.cfg is changed, and settings are saved

Checklist of files to include

Additional information & file uploads

cura.log

smartavionics commented 2 years ago

Shouldn't the path be ~/.config/cura/4.12.0/cura.cfg ?

nallath commented 2 years ago

Shouldn't the path be ~/.config/cura/4.12.0/cura.cfg ?

Yep. That's the one it reads. I've just double checked this on my machine.

Blue-Beaker commented 2 years ago

Shouldn't the path be ~/.config/cura/4.12.0/cura.cfg ?

On my device it's ~/.local/share/cura/4.12/cura.cfg.

smartavionics commented 2 years ago

AFAIK, that's an old name and the presence of that file stops it reading the other one? 

Blue-Beaker commented 2 years ago

I tried to rename 4.12 to 4.12.0 , then cura ignores the config files and appears as a fresh install. also, cura.cfg is not created at all. all settings related to cura.cfg remains cura defaults after changing settings and restarting.

nallath commented 2 years ago

But is there a file in ~/.config/cura/4.12/cura.cfg? What happens if you change that?

Ghostkeeper commented 2 years ago

It should store it in ${XDG_CONFIG_HOME}/cura/4.12/cura.cfg. So if that environment variable is adjusted, it may store it somewhere else.

If the environment variable doesn't exist, it'll store it in ~/.config/cura/4.12/cura.cfg.

no-response[bot] commented 2 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Blue-Beaker commented 2 years ago

But is there a file in ~/.config/cura/4.12/cura.cfg? What happens if you change that?

When I change the file manually to modify some settings, cura settings are changed. But when I change settings in cura, this file isn't changed.

Ghostkeeper commented 2 years ago

Could it be that the file has somehow gotten the wrong permissions?

When Cura is ran as root, the files it creates are also owned by root. Running Cura later as a normal user would prevent modifying the file.

What is the output of running ls -l ~/.config/cura/4.12/cura.cfg in a terminal?

no-response[bot] commented 2 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Blue-Beaker commented 1 year ago

I noticed that cura loads config from ~/.local/share/cura/5.2/cura.cfg, but after config changes it saves to ~/.config/cura/5.2/cura.cfg.
When I copy the second file to replace the first file, cura loads modified configs correctly on next boot. And I've found a workaround for this: symlink ~/.config/cura/5.2/cura.cfg to ~/.local/share/cura/5.2/cura.cfg. After updating cura, recreate the link for the new version.
I guess it's a bug about config paths. The fix should be really simple, just save config to the path where it was read from.

IH303 commented 1 month ago

I noticed that cura loads config from ~/.local/share/cura/5.2/cura.cfg, but after config changes it saves to ~/.config/cura/5.2/cura.cfg. When I copy the second file to replace the first file, cura loads modified configs correctly on next boot. And I've found a workaround for this: symlink ~/.config/cura/5.2/cura.cfg to ~/.local/share/cura/5.2/cura.cfg. After updating cura, recreate the link for the new version. I guess it's a bug about config paths. The fix should be really simple, just save config to the path where it was read from.

I had the same issue. Creating a symlink fixed it for me. Thank you! I hope the devs will fix this