Deluge
Custom Query (2449 matches)
Results (220 - 222 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3000 | Duplicate | 1.3.14 fails to respond properly to choosing which files one wants to download. | Prods | |
| Description |
1.3.14 fails to respond properly to choosing which files one wants to download from within a torrent. For example, I start a torrent but only want to download 5 of the 50 files within the torrent so I high-light those I do NOT want and choose "Do Not Download." Note that Deluge 1.3.14 has a lot of difficulty designating the files as "Do Not Download" and several attempts are often necessary... Expected behaviour is that Deluge will ignore those files designated as "Do Not Download", and only download the files designated as "Normal, High, or Highest" priority. What occurs: Deluge completely messes it up, and files that are designated "Do Not Download" are downloaded; files that are designated "Normal Priority" etc. are only partially downloaded, or not at all. Also, if the 50 files have a total size of 50MB, and the files designated "Normal Priority" etc., have a total size of 5MB, the "Size" column will read some random number that is much larger than the expected 5MB. Running a Force ReCheck? does nothing to fix it. It is a total disaster. Installed via ppa on Xubuntu Xenial. I have confirmed this on both my Xenial systems. Purged ppa and returned to 1.3.12 and everything works fine. |
|||
| #2999 | Fixed | Swedish translation updated | jony0008 | |
| Description |
The Swedish translation has been updated https://translations.launchpad.net/deluge. Please add it to the next Deluge release. |
|||
| #2997 | WontFix | Adding torrent through JSON API fails due to "Invalid JSON request content-type: text/plain;charset=UTF-8" | krichter | |
| Description |
Adding torrents to the Web UI through the BitTorrent? WebUI+ 0.2.3.0.1-signed.1-signed in Firefox 52.0 add-on fails due to 23:58:29.437 [INFO ][twisted :154 ] "192.168.179.4" - - [14/Mar/2017:22:58:29 +0000] "POST /json HTTP/1.1" 200 5987 "https://richtercloud.de:8112/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0" 23:58:30.688 [ERROR ][deluge.ui.web.json_api :212 ] Invalid JSON request content-type: text/plain;charset=UTF-8 23:58:30.688 [INFO ][twisted :154 ] "192.168.179.4" - - [14/Mar/2017:22:58:30 +0000] "POST /json HTTP/1.1" 200 140 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0" 23:58:30.711 [ERROR ][deluge.ui.web.json_api :212 ] Invalid JSON request content-type: text/plain e.g. for magnet:?xt=urn:btih:QWGMQ5G32JBJPZAOSAFRDOG4SLXX46IZ from http://linuxtracker.org/?page=torrents&search=voyager&category=0&active=0 I'm not sure whether this is a deluge bug, but I assume that it is because the logger severity is ERROR. experienced with 2.0.0.dev6970+5348465+201703142101~ubuntu16.10.1 on Ubuntu 16.10 |
|||
