search

dw-0 / kiauh

Klipper Installation And Update Helper
GNU General Public License v3.0
3.43k stars 496 forks source link

Running the new alpha, I see Client-Config: Conflict! in the main menu #517

Closed william-orange closed 2 months ago

william-orange commented 2 months ago

Linux Distribution

Raspian

What happened

I upgraded the the new alpha release. The system continues to run normally and I can do updates in kiauh normally. However I see the "error message" on the main menu Client-Config: Conflict! . I have no idea what this means. A Reddit user sugested to another user that the listen:80 statement could be duplicated between fluiddpi and mainsail. I only have mainsail installed and it starts fine.

What did you expect to happen

No error messages.

How to reproduce

Not sure what it would take to reproduce this. Maybe install Fluiddpi, uninstall and install Mainsail might do it.

Additional information

No response

dw-0 commented 2 months ago

The conflict warning means, that KIAUH detected 2 client-configs on your system. That means you seem to have both, mainsail-config and fluidd-config, downloaded at some point in time. And maybe you even have both of them included in your printer.cfg.

You should doublecheck if really both config repos are present in your users home directory. It is usually not recommended using mainsail-config and fluidd-config at the same time, as it can result in unexpected configuration states or overwrites. Usually both configs do the same, so it is fine to use only one of them. You are not forced to do so though, you can ignore the conflict warning in KIAUH if you really don't care. Klipper, Moonraker, Mainsail and Fluidd will continue to work (but again, maybe there are some sideeffects due to those duplicate config repos).

It has nothing to do with any of the listen ports of the webinterface.

william-orange commented 2 months ago

That makes sense. The fluidd-config file did not show within the klipper directory listing. However, using putty, the folder was there. I had to answer 'yes' to remove a couple of read only files, but rm -r was sucessful. Problem solved.