Correctly remove torrent from queue before exiting. #14883

New issue

Open

opened 2026-02-22 01:32:06 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 01:32:06 -05:00

Owner

Originally created by @lelicopter on GitHub (Aug 13, 2023).

Suggestion

With turn on option "On Downloads done" ->"Exit qBittorent", and with turn on option "When seedings time reaches = 0" then "Remove torrent" need to fix operation. Otherwise torrent still present at next start, but if file already deleted it freeze at queue with error (file not exist). But if at queue more that one torrents, then all correct: except last one, all other removes from list at dowloading finish and app exiting.

Use case

Check on "On Downloads done" ->"Exit qBittorent"
Check on "When seedings time reaches = 0" and "Remove torrent"
At first time, at auto exit, check on "Never show again".

Extra info/examples/attachments

Originally created by @lelicopter on GitHub (Aug 13, 2023). ### Suggestion With turn on option "On Downloads done" ->"Exit qBittorent", and with turn on option "When seedings time reaches = 0" then "**Remove torrent**" need to fix operation. Otherwise torrent still present at next start, but if file already deleted it **freeze at queue** with error (file not exist). But if at queue more that one torrents, then all correct: except last one, all other removes from list at dowloading finish and app exiting. ### Use case Check on "On Downloads done" ->"Exit qBittorent" Check on "When seedings time reaches = 0" and "Remove torrent" At first time, at auto exit, check on "Never show again". ### Extra info/examples/attachments ![image](https://github.com/qbittorrent/qBittorrent/assets/7682951/d0d23c92-cb2c-4b95-b103-c83626a5245b)

deekerman added the

Feature request

Triggers

labels

2026-02-22 01:32:06 -05:00

deekerman commented

2026-02-22 01:32:10 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**