Opened 13 years ago

Closed 13 years ago

Last modified 7 years ago

#1917 closed bug (Fixed)

UnicodeDecodeError with long torrent names

Reported by: OmegaPhil Owned by:
Priority: major Milestone: 2.x
Component: Console (new ncurses) Version: master
Keywords: Cc: nick, non7top@gmail.com

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

Attachments (2)

errors.log (9.2 KB ) - added by OmegaPhil 13 years ago.
Log of errors
0002-Fix-UnicodeDecodeError-with-long-torrent-names.patch (1.1 KB ) - added by Calum 13 years ago.

Download all attachments as: .zip

Change History (10)

by OmegaPhil, 13 years ago

Attachment: errors.log added

Log of errors

comment:1 by OmegaPhil, 13 years ago

One torrent was seeding for testing purposes: [gg]_Sacred_Seven_-_06_[6A405769].mkv

comment:2 by Calum, 13 years ago

Cc: nick added

I think this is the correct fix for the problem.

comment:3 by Calum, 13 years ago

Summary: exceptions.UnicodeDecodeError on connecting deluge-console to delugedUnicodeDecodeError with long torrent names

comment:4 by OmegaPhil, 13 years ago

I can confirm the console ui works now.

comment:5 by Vladimir Berezhnoy, 13 years ago

Cc: non7top@gmail.com added

I can confirm that this patch applies to 7227c97cacd6c3a7a1cf3d75e8dcd04e0eb71693 and fixes the issue.

comment:6 by Vladimir Berezhnoy, 13 years ago

This still applies to current git master and does fix the issue. Please commit the patch to git.

comment:7 by Calum, 13 years ago

Resolution: fixed
Status: newclosed

Thanks, I knew I had missed one :)

Fixed in master: 9d16b500

comment:8 by Calum, 7 years ago

Milestone: 2.0.x2.x

Milestone renamed

Note: See TracTickets for help on using tickets.