Custom Query (2447 matches)


Show under each result:

Results (43 - 45 of 2447)

Ticket Resolution Summary Owner Reporter
#190 Fixed Share ratio / upload statistics bug andar

The seeding limit was set to 200% in preferences. The torrent finished downloading and kept uploading. When it reached 200%, it stopped seeding and the gui showed that I have seeded over 500%. Every time I clicked on resume my share ratio was increased by 200%, but the seeding did not restart.

#192 WorksForMe deluged 0.6 crashes with python error andar

Deluged doesn't seem to like starting at times. If I first turn the computer on, it seems to load the daemon ok. But if I shut the daemon down and then start it again, I get this python error:

[DEBUG   ] torrent:542 Attempting to save torrent file: heroes.torrent
[DEBUG   ] pluginmanager:147 run_post_session_load
Traceback (most recent call last):
  File "/usr/bin/deluged", line 7, in ?
  File "/usr/lib/python2.4/site-packages/deluge/", line 101, in start_daemon
    Daemon(options, args)
  File "/usr/lib/python2.4/site-packages/deluge/core/", line 44, in __init__
    self.core = Core(options.port).run()
  File "/usr/lib/python2.4/site-packages/deluge/core/", line 252, in run
  File "/usr/lib/python2.4/site-packages/deluge/", line 194, in start
  File "/usr/lib/python2.4/site-packages/deluge/", line 114, in start
  File "/usr/lib/python2.4/site-packages/deluge/", line 121, in start_component
  File "/usr/lib/python2.4/site-packages/deluge/", line 126, in start_component
  File "/usr/lib/python2.4/site-packages/deluge/core/", line 150, in start
  File "/usr/lib/python2.4/site-packages/deluge/core/", line 532, in load_state
KeyError: 'dcd81b918cfc6ddfd150025b7271f3c8bb4446b4'

This is when clicking on start daemon in the webui but the same happens with the gtkui. I've got deluge 0.6 running fine on my ubuntu hardy computer but not on my gentoo computer. Is it because I'm using python-2.4 on gentoo?

#193 Fixed Uploaded data amount increases when pausing/changin queue order andar anonymous

There is a bug in that increases the amount of uploaded data (and thereby the share ratio) when a torrent is paused or the order in the queue is changed (it does not appear however when the method of sorting is changed).

To reproduce:

Take a torrent having uploaded a fair amount of data during this session (preferably at least 10% of the total uploaded amount, that way it is more visible). When this torrent is paused or its queue order is changed (by moving it either up or down by one place or by queuing it to the top/bottom), the amount of uploaded data will increase by the amount already uploaded during this session. Also, when you change the queue order, every torrent that also changes queue order by this act will undergo the same increase.


In, the function pickle_state, which is supposed to write the statistics of the torrent in a file in case of a crash or upon closing, saves the amount of uploaded data to torrent.uploaded_memory. The problem is that this function is also called when changing queue order (by the functions queue_top, queue_up, queue_down and queue_bottom) and upon pausing (by set_user_pause), so that any of these actions transforms the amount U of uploaded data into U+x where x is the amount of data uploaded during the current session, so that after n of the actions, your uploaded data amounts to U+n*x; the solution is to either disable pickle_state in these cases (what I have done on my own client as a quick fix, I do not mind the higher vulnerability against crashed that much if it keeps my ratio safe) or to modify the function so as to only save to an external variable that will be restored upon starting Deluge.

Also, so far I have only seen reports of this problem on systems running linux (Ubuntu 8.04 to be more precise, see and, but I suppose that this could also happen under other operating systems (I did not test this though, so I might be wrong).

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.