Send a notification when qBitTorrent is exiting #14649

New issue

Open

opened 2026-02-22 01:17:14 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 01:17:14 -05:00

Owner

Originally created by @freonpsandoz on GitHub (Jun 1, 2023).

Suggestion

Depending on how long qBitTorrent has been running, shutting it down can now take 10 minutes or more for it to do whatever it needs to do before it's actually ready to shut down. By that time, I've completely forgotten that I told it to shut down, not to mention why I did so. If it isn't possible for it to always shut down quickly, it would be nice if it could send a notification just before it actually exits to remind the user.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @freonpsandoz on GitHub (Jun 1, 2023). ### Suggestion Depending on how long qBitTorrent has been running, shutting it down can now take 10 minutes or more for it to do whatever it needs to do before it's actually ready to shut down. By that time, I've completely forgotten that I told it to shut down, not to mention why I did so. If it isn't possible for it to always shut down quickly, it would be nice if it could send a notification just before it actually exits to remind the user. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Triggers

labels

2026-02-22 01:17:14 -05:00

deekerman commented

2026-02-22 01:17:21 -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.)**