starred/qBittorrent

Fork 0

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

[Bug] torrents with the same file names cause mess #3602

New issue

Closed

opened 2026-02-21 16:51:55 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 16:51:55 -05:00

Owner

Originally created by @Snurre86 on GitHub (Dec 19, 2015).

If two or more torrents with the same (payload) folder and file names have the same save path allot of mess happens.

You can not change the save path of either torrent if they are started as both torrents will claim the files and fight over them (even if paused after started). To work around this you actually have to delete all torrents and add them again?
If you manage to change the save path for one of the torrents you can not open it with "Open destination folder" in the context menu as you only get the first save path not the save path you changed to.
If you manage to change the save path of one of the torrents you get an endless spiral of sub folders with the (payload) folder name and each will get a copy of the torrents files.

Also see: #4350

Originally created by @Snurre86 on GitHub (Dec 19, 2015). If two or more torrents with the same (payload) folder and file names have the same save path allot of mess happens. 1. You can not change the save path of either torrent if they are started as both torrents will claim the files and fight over them (even if paused after started). To work around this you actually have to delete all torrents and add them again? 2. If you manage to change the save path for one of the torrents you can not open it with "Open destination folder" in the context menu as you only get the first save path not the save path you changed to. 3. If you manage to change the save path of one of the torrents you get an endless spiral of sub folders with the (payload) folder name and each will get a copy of the torrents files. Also see: #4350

deekerman

2026-02-21 16:51:55 -05:00

closed this issue
added the
autoCloseOldIssue
label

deekerman commented

2026-02-21 16:51:59 -05:00

Author

Owner

@Snurre86 commented on GitHub (Jan 8, 2016):

Was able to reproduce again today. Having two torrents downloading the same content (also names) to the same save path then realizing it and changing the folder on one of the torrents will cause a lot of mess. First qbt will try to move the files to the new save path and it happens sometimes and the other torrent will face errors. also the destination folder will be set but you can not open it from "open destination folder" from the context menu as it will only show you the first destination folder then it will create an endless spiral of folders inside folders with copy's of the torrent files.

@Snurre86 commented on GitHub (Jan 8, 2016): Was able to reproduce again today. Having two torrents downloading the same content (also names) to the same save path then realizing it and changing the folder on one of the torrents will cause a lot of mess. First qbt will try to move the files to the new save path and it happens sometimes and the other torrent will face errors. also the destination folder will be set but you can not open it from "open destination folder" from the context menu as it will only show you the first destination folder then it will create an endless spiral of folders inside folders with copy's of the torrent files.

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jan 8, 2016):

Was able to reproduce again today.

Is it always 100% reproducible?

Having two torrents downloading the same content (also names) to the same save path then realizing it and changing the folder on one of the torrents will cause a lot of mess.

How can you download 2 identical torrents at the same time? Won't qBt tell you it's already downloading? You'll have to elaborate more here.

@Chocobo1 commented on GitHub (Jan 8, 2016): > Was able to reproduce again today. Is it always 100% reproducible? > Having two torrents downloading the same content (also names) to the same save path then realizing it and changing the folder on one of the torrents will cause a lot of mess. How can you download 2 identical torrents at the same time? Won't qBt tell you it's already downloading? You'll have to elaborate more here.

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@Snurre86 commented on GitHub (Jan 9, 2016):

Won't qBt tell you it's already downloading?

What happens is that the torrents are not identical (I think) but the folders and files have the same name in them and it becomes a mess as you can't even change the save path after both has started as both torrents will claim the files and fight over them so to speak.

Is it always 100% reproducible

I do report as I find bugs but I do not on purposes right now try to make to much mess out of things.

@Snurre86 commented on GitHub (Jan 9, 2016): > Won't qBt tell you it's already downloading? What happens is that the torrents are not identical (I think) but the folders and files have the same name in them and it becomes a mess as you can't even change the save path after both has started as both torrents will claim the files and fight over them so to speak. > Is it always 100% reproducible I do report as I find bugs but I do not on purposes right now try to make to much mess out of things.

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@Snurre86 commented on GitHub (Jan 13, 2016):

Updated the first comment, give me feedback if you understand it or not.

@Snurre86 commented on GitHub (Jan 13, 2016): Updated the first comment, give me feedback if you understand it or not.

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@Snurre86 commented on GitHub (Jan 24, 2016):

No feedback received, might just close this issue?

@Snurre86 commented on GitHub (Jan 24, 2016): No feedback received, might just close this issue?

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@Lillecarl commented on GitHub (Feb 2, 2019):

I accidentally reproduced this today after downloading for hours. Mean bug, especially since the files were not to be found in the bin or anything.

@Lillecarl commented on GitHub (Feb 2, 2019): I accidentally reproduced this today after downloading for hours. Mean bug, especially since the files were not to be found in the bin or anything.

deekerman commented

2026-02-21 16:52:00 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.

deekerman referenced this issue

2026-02-21 16:52:54 -05:00

Lost destination of completed files #3633