starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

paused torrent files recreated #54

New issue

Closed

opened 2026-02-21 14:50:30 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-21 14:50:30 -05:00

Owner

Originally created by @archish on GitHub (Aug 26, 2012).

Version 3.0.1 OS: Linux, Ubuntu 12.04

When a torrent is in paused state and the files are physically moved or deleted using the file manager the qBT client recreates these files. Ideally until the torrent is started/resumed again the file should not be recreated or an option called Stop should be provided similar to utorrent.

Steps to Reproduce:

Select a completed/seeding torrent and put in paused state.
Via file manager move or delete the torrent related files/folders.
Close and reopen qBT, the empty folder are recreated for the paused torrent.

Originally created by @archish on GitHub (Aug 26, 2012). Version 3.0.1 OS: Linux, Ubuntu 12.04 When a torrent is in paused state and the files are physically moved or deleted using the file manager the qBT client recreates these files. Ideally until the torrent is started/resumed again the file should not be recreated or an option called Stop should be provided similar to utorrent. Steps to Reproduce: 1) Select a completed/seeding torrent and put in paused state. 2) Via file manager move or delete the torrent related files/folders. 3) Close and reopen qBT, the empty folder are recreated for the paused torrent.

deekerman closed this issue

2026-02-21 14:50:34 -05:00

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@bobthebigbat commented on GitHub (Nov 3, 2012):

Can we simply have an option to STOP completed torrents the same way utorrent does (the torrent should be in the "Completed" and "All" states and possibly "Inactive", but not "Paused").

Once a torrent has completed (and reached the specified seed ratio) the torrent should be stopped (not paused), which essentially keeps the torrent in the list, but no longer updates/checks the trackers.
I used this feature of utorrent to help me keep track of recently completed torrents. I was able to select only a few individual files from a torrent, have them complete, the torrent STOP, then days or weeks later, I could select a few more files from the torrent and have them download ... rinse and repeat.
It also let me delete/move the downloaded files manually, without it trying to redownload them.

You would also need to add a setting to the combo box in Options --> BitTorrent --> Share Ratio Limiting

@bobthebigbat commented on GitHub (Nov 3, 2012): Can we simply have an option to STOP completed torrents the same way utorrent does (the torrent should be in the "Completed" and "All" states and possibly "Inactive", but not "Paused"). Once a torrent has completed (and reached the specified seed ratio) the torrent should be stopped (not paused), which essentially keeps the torrent in the list, but no longer updates/checks the trackers. I used this feature of utorrent to help me keep track of recently completed torrents. I was able to select only a few individual files from a torrent, have them complete, the torrent STOP, then days or weeks later, I could select a few more files from the torrent and have them download ... rinse and repeat. It also let me delete/move the downloaded files manually, without it trying to redownload them. You would also need to add a setting to the combo box in Options --> BitTorrent --> Share Ratio Limiting

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@junpet commented on GitHub (Feb 10, 2013):

I agree with bobthebigbat. I want STOP button, please!

@junpet commented on GitHub (Feb 10, 2013): I agree with bobthebigbat. I want STOP button, please!

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jan 12, 2017):

Now the affected torrent go into "Missing Files" status which requires manual intervention as long as the files are missing.
@Balls0fSteel

@thalieht commented on GitHub (Jan 12, 2017): Now the affected torrent go into "Missing Files" status which requires manual intervention as long as the files are missing. @Balls0fSteel

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Jun 6, 2017):

@thalieht @archish The title of this issue is misleading IMO. Just tested this in 3.3.13, with a torrent with a single root folder; here is what I observed after following the steps outlined in the OP:

Only the empty folder was recreated, not the files themselves.

@FranciscoPombal commented on GitHub (Jun 6, 2017): @thalieht @archish The title of this issue is misleading IMO. Just tested this in 3.3.13, with a torrent with a single root folder; here is what I observed after following the steps outlined in the OP: Only the empty _folder_ was recreated, not the _files_ themselves.

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 6, 2017):

Just tested in 3.3.12. Nothing is recreated for me.

@thalieht commented on GitHub (Jun 6, 2017): Just tested in 3.3.12. Nothing is recreated for me.

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Jun 6, 2017):

@thalieht Interesting, did the torrent you tested with have all files on top level or did it have o root folder with all files in it?

@FranciscoPombal commented on GitHub (Jun 6, 2017): @thalieht Interesting, did the torrent you tested with have all files on top level or did it have o root folder with all files in it?

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 6, 2017):

I tested both with the same outcome. I'm gonna test 3.3.13 in a while to see if it matters. Probably doesn't matter but i'm on win 7.

@thalieht commented on GitHub (Jun 6, 2017): I tested both with the same outcome. I'm gonna test 3.3.13 in a while to see if it matters. Probably doesn't matter but i'm on win 7.

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 6, 2017):

Still nothing in 3.3.13.

@thalieht commented on GitHub (Jun 6, 2017): Still nothing in 3.3.13.

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Jun 6, 2017):

@thalieht ok, maybe I did something wrong when testing this.
@evsh @Chocobo1 @sledgehammer999 can somebody else also test this please?

@FranciscoPombal commented on GitHub (Jun 6, 2017): @thalieht ok, maybe I did something wrong when testing this. @evsh @Chocobo1 @sledgehammer999 can somebody else also test this please?

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 6, 2017):

In another issue you mentioned you use ".!qB". I wanna say i haven't tested with it nor using an incomplete folder.

@thalieht commented on GitHub (Jun 6, 2017): In another issue you mentioned you use ".!qB". I wanna say i haven't tested with it nor using an incomplete folder.

deekerman commented

2026-02-21 14:50:37 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 6, 2017):

Yep, found the culprit! When i have ".!qB" enabled it indeed creates an empty folder!

@thalieht commented on GitHub (Jun 6, 2017): Yep, found the culprit! When i have ".!qB" enabled it indeed creates an empty folder!

deekerman commented

2026-02-21 14:50:38 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang commented on GitHub (Sep 16, 2018): We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0). Please, update to last release and, if the bug/error/crash is still present, open another issue. Thank you.