Bug 698445 - Ktorrent not moving downloaded files to a different folder, even though configured
Summary: Ktorrent not moving downloaded files to a different folder, even though confi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ktorrent
Version: 14
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Roland Wolters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 21:39 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-03 02:24:13 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Kovalsky 2011-04-20 21:39:22 UTC 
I've noticed during the last week or two that ktorrent stopped moving downloaded (finished) files into a different folder. 

I have this setup in preferences (see screenshot). 

Unfortunately I had only 200 lines setup in the log viewer plugin, so I could go only about 10 minutes back (where nothing interested is showed). I've raised the limit to 20000 and will see next time I hit this. 

ktorrent-4.1.0-1.fc14.x86_64
Comment 1 nucleo 2011-04-30 12:57:55 UTC 
See http://ktorrent.org/forum/viewtopic.php?f=2&t=4045
Comment 2 Roland Wolters 2011-12-29 11:38:02 UTC 
David, the mentioned link does mention that changes of the option only applies to torrents which has been started after the change. Can you please verify that the option is set and that even torrents started after setting the option are not moved at all?
Comment 3 David Kovalsky 2012-01-02 13:09:14 UTC 
Hi, 

I recall testing that on F14 and it still wasn't working. 

But now, without changing anything, just updating to F16 (ktorrent-4.1.3-1.fc16.x86_64), everything works like charm. 

Since F14 is at the end of lifetime, I don't mind if this gets closed as it's fixed in F16.
Comment 4 Rex Dieter 2012-01-03 02:24:13 UTC 
thanks for checking.
Note You need to log in before you can comment on or make changes to this bug.