This issue was caused by an unclean shutdown of Deluge, usually on system shutdown, and upon rebooting
the PID stored in the lockfile is in used by another process thus the lockfile is never removed. It
affects users with Deluge set in startup applications as the PIDs are more likely to be reused.
* Lockfile is removed if Deluge is restarted in IPC.
* Renamed the old_tempfile variable to make it clearer as to it's role.
* Remove duplicate entry in init.
* Call update if empty config and prevent potential loop in update method.
* Ensure that the queue Add button is sensitive, even when automatically adding.
This negates the need for quoting a single command with an arg e.g.
deluge-console del --remove_data torrrent_file
Multiple commands separated by semi-colon still require quoting.
The code in develop is more robust but by writing to a temp file first
then moving it should stop the worst of fastresume corruption issues,
e.g. hard resets.
json.dumps attempts to decode (utf8) the 'path' entry which had a
different encoding. The solution is to ensure the 'path' entry is
utf8 encoded and remove the unneeded 'path.utf-8' entry.
As self.__m_metadata["info"]["files"] is updated the later code
checking and decoding the 'path' entry can be removed.
When adding a torrent already in session any new trackers are merged
to the exiting torrent but this is an unwanted feature for private
flagged torrents.
Created a generic password dialog and moved the unlock code out of
systemtray so any call to window.present will now show the dialog.
Also fixed the appindicator not showing the correct visible status
On Mavericks the application path passed to scripts only has single leading slash
compared to previous double slash.
Renamed and changed shebang to bash to prevent any issues.
Updated README to rst format for display in trac wiki.
This ensures that only ip addresses are accepted for
listen_interface as libtorrent cannot accept interface
names (eth0) and will cause unexpected results for user.