Deluge Forum

Hi,

I have been using Deluge 0.5.8.9 with Ubuntu Hardy Heron LTS for some time now and have been very happy with it. It is fast, efficient and hardly uses any CPU even when pulling 700+ Kbps from my ADSL line.

Earlier today, after a couple of days operation, the Network Activity Graph stopped updating.

I stopped and restarted Deluge but still no graph.
I deactivated and reactivated the plugin, still no joy.
I uninstalled Deluge and reinstalled it, still no joy.
I deleted the graph.conf file, still no joy.

In short, the Network Activity Graph plugin (one of my favourite features) has stopped working and nothing I do will make it start!

Any suggestions?

Hi,

This has been bugging me and a bit of further research reveals the problem lies in the persistant.state file as deleting this file restores my beloved graph to its former glory. Obviously I also lose all my other settings which is not acceptable so I have restored the original contents.

Having looked at the aforementioned file it appears to have a fairly simple list structure a la Lisp so if someone could point me to the relevant documentation I will whizz through it, locate the offending parameter, fix it and post my findings.

Regards
Fred

fred wrote:Hi,

This has been bugging me and a bit of further research reveals the problem lies in the persistant.state file as deleting this file restores my beloved graph to its former glory. Obviously I also lose all my other settings which is not acceptable so I have restored the original contents.

Having looked at the aforementioned file it appears to have a fairly simple list structure a la Lisp so if someone could point me to the relevant documentation I will whizz through it, locate the offending parameter, fix it and post my findings.

Regards
Fred

It is a pickled object. Just google python pickle for more information.

Hi again,

Having never programmed in Python before (but being an experienced programmer) it might take me a little while to get to the bottom of this. I'm burrowing into the language docs right now but when I emerge from the other side (hopefully with the answer) I will be back in contact...

Regards
Fred

Hi,

Me again. After examing the code (Python is very similar in many repects to: C, Algol 68 and Perl) and adding some debugging in the core.py module (I like the PrettyPrinter BTW) I conclude the persistent.state file only really contains details of the active torrent files so concluded that was not what was causing the problem. Progressing with the analysis I deleted the persistent.state file and after confirming the Network Activity Graph (NAG) was working correctly I loaded the torrents back in one by one.

Everything was fine until one particular torrent file was loaded. At this point the NAG changed, although the screen continued to be updated the values displayed remained the last ones (prior to the torrent being loaded) regardless of the actual network activity. Removing the offending torrent caused the NAG to resume its correct operation.

Something I failed to notice before, as well as the NAG not updating properly, the staus bar at the bottom of the application does not update either and this situation perists as long as the offending torrent is active. However, if it is paused (or removed) both the NAG and status bar update correctly.
Also, I do not recall having seen any download / upload activit on the main torrent display or on the Details and Peers tabs but as it is at 41% I complete have to assume there has been some activity.

I had to conclude something in that torrent file is affecting the operation of the Network Activity Graph plugin and the status bar..

In order to test my hypothesis I examined as many torrentfiles as I could locate on my system and as the offending torrent was the only one to include HTML in the comments section I have to conclude this to be the source of the problem. I would be most grateful if you could let me know if my investigations have been helpful and my conclusions correct as deluge is the best torrent client I have used to date and knowing I had helped to improve it would give me a warm feeling...

Regards
fred

We don't support the old 0.5.x branch.. If you have an issue with the latest release, then we can work to fix that.