Specifiing a new config dir leads to permission denied error

[peterke@gmail.com]

When starting the deluge daemon, there is an option to specify where the config directory is, but besides putting the log file there, the program ignores the option and tries to create it's own config dir in the users home directory.

This way it is impossible to start it under SUSE during boot time, as then no HOME environmental variable is set, thus Deluge tries to create the .config folder in the file system root. (Even though it was specified to use a different folder).

With just a quick look through, the problem seems to be in the configmanager.py file in the class constructor: the self.config_directory is always initialized to the *default* config dir, even though it was overridden on startup. In the daemon.py file the config dir variable is later set to the correct *new* config folder, but the execution never reaches this line (the overriding of the *default* config dir), as when it loads the *default* it already dies with a permission denied error.

[andar]

This should be fixed in [3714]

[(none)]

Milestone 1.0.0 deleted