#1976: Deluge puts torrents into obfuscated random-character directories on
completion.
-------------------+--------------------------------------------------------
Reporter: fuxxy | Owner: Cas
Type: bug | Status: accepted
Priority: minor | Milestone: 1.3.4
Component: other | Version: 1.3.3
Keywords: |
-------------------+--------------------------------------------------------
Changes (by Cas):
* owner: => Cas
* status: new => accepted
* milestone: 1.3.x => 1.3.4
Old description:
> First of all, I'm an idiot. This was all my doing. However, it could
> happen in the future to someone else, hence the bug report.
> My setup consists of a linux fileserver running the deluge daemon, I'm
> connecting via a remote GUI on a windows computer. Both the deluge daemon
> and the client are 1.3.3, using libtorrent 0.15.6.0
>
> In the "move completed" option, I specified an absolute directory path .
> To make things easier on myself, in PuTTY, I simply "cd" to the path I
> wanted, then did a 'pwd'. Afterwards, it was as simple as triple clicking
> the PuTTY window to select the whole line, and paste it into the Deluge
> client. It appears some special characters made it from PuTTY into
> Deluge.
>
> RESULTING OPERATION:
> Anything I specified via a triple click from PuTTY ended up in a
> directory with special characters. Using Windows navigating to the linux
> samba share, the directory appeared as completely random characters, in
> this case "SESKUE~M". Navigating to the same directory under linux
> results in two possible outcomes:
> deluge@coldfire /shared/TV_Shows/TV Series $ ls -alh
> total 12K
> drwxrwsr-x 6 deluge video 67 Nov 21 10:22 .
> drwxrwsrwx 58 apache video 4.0K Nov 21 07:40 ..
> drwxrwsr-x 2 deluge video 4.0K Aug 12 2010 Season 1
> drwxrwxr-x 2 deluge video 6 Nov 20 17:19 Season 2
> drwxr-sr-x 3 deluge video 56 Nov 21 10:22 Season 2?
> drwxrwxr-x 2 deluge video 4.0K Nov 14 19:10 Season 3
>
> deluge@coldfire /shared/TV_Shows/TV Series $ cd Season\
> Season 1/ Season 2/ Season 2!^J/ Season 3/
>
> EXPECTED OUTCOME:
> Possibly parse the "move completed" and "move storage" options to
> eliminate special characters?
New description:
First of all, I'm an idiot. This was all my doing. However, it could
happen in the future to someone else, hence the bug report.
My setup consists of a linux fileserver running the deluge daemon, I'm
connecting via a remote GUI on a windows computer. Both the deluge daemon
and the client are 1.3.3, using libtorrent 0.15.6.0
In the "move completed" option, I specified an absolute directory path .
To make things easier on myself, in PuTTY, I simply "cd" to the path I
wanted, then did a 'pwd'. Afterwards, it was as simple as triple clicking
the PuTTY window to select the whole line, and paste it into the Deluge
client. It appears some special characters made it from PuTTY into Deluge.
RESULTING OPERATION:
Anything I specified via a triple click from PuTTY ended up in a directory
with special characters. Using Windows navigating to the linux samba
share, the directory appeared as completely random characters, in this
case "SESKUE~M". Navigating to the same directory under linux results in
two possible outcomes:
{{{
deluge@coldfire /shared/TV_Shows/TV Series $ ls -alh
total 12K
drwxrwsr-x 6 deluge video 67 Nov 21 10:22 .
drwxrwsrwx 58 apache video 4.0K Nov 21 07:40 ..
drwxrwsr-x 2 deluge video 4.0K Aug 12 2010 Season 1
drwxrwxr-x 2 deluge video 6 Nov 20 17:19 Season 2
drwxr-sr-x 3 deluge video 56 Nov 21 10:22 Season 2?
drwxrwxr-x 2 deluge video 4.0K Nov 14 19:10 Season 3
deluge@coldfire /shared/TV_Shows/TV Series $ cd Season\
Season 1/ Season 2/ Season 2!^J/ Season 3/
}}}
EXPECTED OUTCOME:
Possibly parse the "move completed" and "move storage" options to
eliminate special characters?
--
Comment:
I already implemented a sanitize function for renaming files/folders and
there are very few characters that are restricted on linux however just
realised that we are talking about 'move completed' which is different
piece of code.
So we could run the sanitize function in move_storage and/or when
move_completed is specified in the ui. Oh and I don't think that the
decoding to unicode helped matters.
fuxxy: It would be helpful if you could repeat this with debug logging
enabled on deluged as the 'move completed' option is logged and should
shed some light on the precise issue.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/1976#comment:4>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
