Custom Query (2449 matches)
Results (658 - 660 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1917 | Fixed | UnicodeDecodeError with long torrent names | ||
| Description |
After apparently successfully connecting to a localhost instance of deluged via deluge-console, masses of the following occur: exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 8: ordinal not in range(128) See log attached. Client Version: 1.3.900-dev Libtorrent Version: 0.15.7.0 |
|||
| #1919 | Duplicate | deluge 1.3.3 hangs after <5 minutes | ||
| Description |
installed on windows xp with a wireless router added 3 torrents, works for a little bit transfer stopped, deluge was redrawing, but wasn't responding, had to kill process goodbye |
|||
| #1920 | Duplicate | Checking Torrent Stops at a Random Percentage on Windows | ||
| Description |
The checking of torrents stops suddenly on Windows. The problem occurs very often. It just stops checking at some percentage and refuses to continue. I have to close and start Deluge again for it to continue, but then it starts checking the same torrent again and stops at some point. NOTE: I rolled back to 1.3.2, which does not have the problem. So this should be easy to trace back for you. Also note that there is now a new status for torrents that are checking which is called 're-checking' (or something - I can't remember exactly), which is displayed as status sometimes instead of just checking. This could be related to this. Also in this version some torrents won't respond to pause/resume commands, which is related I think. |
|||
