Bittornado preferences diaog doesn't save the new preferences

It would seem BitTornado 0.3.17-1 on feisty doesn't actually store any configuration settings in one's home folder.

Actually, on the first run, BT creates the .BitTornado folder within one's home, and creates a config.gui.ini file which does store its settings; but if one changes them in the GUI and tries to save them, nothing happens. The file remains untouched, and thus all settings are reset to the defaults upon restarting the program.

While not really a showstopper, this bug is at the very least a major nuisance. It also did not occur with the bittornado/bittornado-gui packages from edgy.

On closer inspection, oddly enough, when changing the configuration through the GUI, the config.gui.ini *does* get changed! However, nothing changes in the file except the date and time on line 2.

After to analize the code. I see that ConfigReader.saveConfitgs doesn't update the value of self.config. And in ConfigDir.saveConfig the funciton saves the iniitial value of self.config and the date its updated.

I'm not a programmer, but i think that this isn't a bug of this program, because in edgy works fine and i don't any differences between the code of the edgy package and the feisty packages.

I think that this could be a Python problem or a configuration problem.

If one changes settings by hand in the file (such as minport and maxport) and reload BitTornado, those settings do stick; they are under no circumstances reset to their respective default values 10000 and 60000; thus BT loads the config.gui.ini file upon launch correctly, but doesn't store information.

Since the package in edgy was version 0.3.15 and the one in feisty is 0.3.17, I guess it's not impossible that this bug crept in in the meantime.

Exactly the same bug here.

http://ubuntuforums.org/showpost.php?p=2614964&postcount=7

Instructions for manual fix.

Ops, sorry. Those instructions were for an specific fix. The common procedure is to edit the file ~/.BitTornado/config.gui.ini and change the settings manually.

This was fixed in 0.3.18-2 and so in gutsy.