Custom Query (2447 matches)
Results (247 - 249 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#3309 | Fixed | TypeError: '>' not supported between instances of 'NoneType' and 'str' | ||
Description |
At start: TypeError: '>' not supported between instances of 'NoneType' and 'str' Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/deluge/ui/gtk3/listview.py", line 233, in stabilized result = sort_func(model, iter1, iter2, data) File "/usr/lib64/python3.6/site-packages/deluge/ui/gtk3/torrentview.py", line 106, in progress_sort return cmp(state1, state2) File "/usr/lib64/python3.6/site-packages/deluge/ui/gtk3/common.py", line 45, in cmp return (x > y) - (x < y) Seems like number of this messages correlates with number of torrents... |
|||
#3310 | Fixed | "Session status key not valid" log spam | ||
Description |
After upgrading my Debian deluge package from 1.3.15-2 to 2.0.3-1, I am faced with the following message being dumped every second or so in the Deluge daemon output: 13:55:31 [WARNING ][deluge.core.core :655 ] Session status key not valid: num_connections 13:55:32 [WARNING ][deluge.core.core :655 ] Session status key not valid: dht_cache_nodes 13:55:32 [WARNING ][deluge.core.core :655 ] Session status key not valid: num_connections 13:55:33 [WARNING ][deluge.core.core :655 ] Session status key not valid: dht_cache_nodes 13:55:33 [WARNING ][deluge.core.core :655 ] Session status key not valid: num_connections My guess is that Deluge 2.0 is confused by old torrents from Deluge 1.3. Any ideas on how to make the log spam stop? |
|||
#3316 | Fixed | Down Speed and Uploaded indicated wrong | ||
Description |
Just look at this picture. Down Speed means Uploaded, Uploaded means Down Speed. (Also what is K/s and G?) |
Note:
See TracQuery
for help on using queries.