Custom Query (2449 matches)
Results (199 - 201 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #266 | WontFix | Wrong ETA when some files of a torrent are not downloaded | ||
| Description |
This bug is present when the user chooses not to download all the files in the torrent. Deluge does not update properly the ETA and gives an estimation over the size of all the files in the torrent and not over just the ones selected for download. It's really annoying because it basically makes ETA useless all those times you are downloading just a small fraction of the files from a torrent. |
|||
| #271 | Invalid | Support socks4a, socks4, socks5 protocols leak dns requests | ||
| Description |
Deluge presently supports the socks4 and socks5 protocols for proxies. These do not support dns requests. The socks4a protocol takes dns requests. Supporting socks4a would mean users using tor would not have their dns requests leaked. Deluge 0.5.8.9 |
|||
| #273 | WorksForMe | Multiple instances of deluge possible | ||
| Description |
On Ubuntu 8.04 32-bit This problem has existed for some time, but I didn't notice because I was using a workaround (telling Deluge to watch a directory and having Firefox download to that directory rather than having Firefox launch Deluge.) If I launch deluge through GNOME, and I try to launch deluge again through GNOME (by clicking an icon in the panel, through a menu, through alt-F2, etc.) then Deluge behaves properly. It sees that an instance of deluge already exists and won't launch another instance. However, if I launch deluge through Firefox or through gnome-terminal, Deluge fails to see that an instance already exists and launches a duplicate instance. I don't think this should happen ;p |
|||
