Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#427 closed bug (Fixed)

Specifiing a new config dir leads to permission denied error

Reported by: peterke@… Owned by: markybob
Priority: critical Milestone:
Component: Core Version: 0.9.05 (1.0.0_RC5)
Keywords: Cc:

Description

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.

Change History (3)

comment:1 Changed 12 years ago by andar

  • Component changed from 0.5.x to core
  • Milestone set to 1.0.0
  • Resolution set to fixed
  • Status changed from new to closed

This should be fixed in [3714]

comment:2 Changed 12 years ago by anonymous

  • Milestone 1.0.0 deleted

Milestone 1.0.0 deleted

comment:3 Changed 11 years ago by alisazhao2009

If you’re a dedicated follower of tiffany co like me. Don't miss the tiffany uk & co. on sale including pendants, necklace, earrings, bracelets on line. tiffanys is the one thing that outlasts the cake, champagne and music.

Note: See TracTickets for help on using tickets.