Closing Daemon causes core.conf to revert to default settings

[hawkeye]

Really loving 2.0x but having a pretty significant issue here when using a daemon with thin clients on linux.

Closing out the daemon cleanly via the ui or systemd will cause a few settings in core.conf to revert to null from settings made from any ui or manual text editor.

"listen_interface" set to ip address in ui or text editor on daemon close reverts to null "listen_random_port" set to false in ui or text editor on daemon close reverts to null

[hawkeye]

core.conf relevant settings

[Calum]

Milestone renamed

[Calum]

You cannot manually modify core.conf while deluged is running, it will be overwritten on every new config setting and shutdown.

I can see no issue with setting changes to listen_interface, however, there appears to be a bug in listen_random_port.

Which UI were you using?

Edit: I don't see any issue with listen_random_port is random_port set to True as that would set listen_random_port to None?

[hawkeye]

here is how it occurs:

Set listen ip address in thin client connected to daemon to 192.168.2.10 hit apply. listen_interface in core.conf reflects the ip address.

If I shutdown the daemon via systemd OR the thin client that IP address will revert to null. I am not changing it while the daemon is running except via the thin client.

I can go in and set the listen address manually it will load the daemon and show the ip address in the thin client network configuration where it should. But once I stop the daemon it reverts to null.

i updated to 2.0.0.dev7223 and the problem occurs. This issue does not occur on the current 1.3.15 version. I have not tested it on the windows version.

[Calum]

Ok I now see the issue now! This is an odd one but I think it might be a text/bytes issue.

Actually found the issue, a mistake in core shutdown code...

[Calum]

Thanks for feedback, fixed is develop: [67d9c2efb4ba9]

[hawkeye]

I concur issue is fixed!