Annoying double notification when torrents finish downloading #11112

Closed
opened 2026-02-21 21:09:33 -05:00 by deekerman · 8 comments
Owner

Originally created by @Bu11etmagnet on GitHub (Oct 25, 2020).

Please provide the following information

qBittorrent version and Operating System

4.3.0.1 on Windows 10

If on linux, libtorrent-rasterbar and Qt version

What is the problem

Double notification when torrents finish downloading. First, the "Finished moving" notification appears. Then, the "Finished downloading" notification appears.
The "Finished moving" notification adds no useful information, especially before the "Finished Downloading" notification. There is no discernable operation after a torrent has been moved to its final place.
Unfortunately, the only way to get rid of it is to disable notifications altogether. Only the notification for added torrents can be individually disabled.

What is the expected behavior

Only one notification appears after the torrent finishes downloading.
There should be at least an option to disable the "Finished moving" notification.

Steps to reproduce

Download any torrent.

Extra info(if any)

(type here)

Originally created by @Bu11etmagnet on GitHub (Oct 25, 2020). **Please provide the following information** ### qBittorrent version and Operating System 4.3.0.1 on Windows 10 ### If on linux, libtorrent-rasterbar and Qt version - ### What is the problem Double notification when torrents finish downloading. First, the "Finished moving" notification appears. Then, the "Finished downloading" notification appears. The "Finished moving" notification adds no useful information, especially *before* the "Finished Downloading" notification. There is no discernable operation after a torrent has been moved to its final place. Unfortunately, the only way to get rid of it is to disable notifications altogether. Only the notification for added torrents can be individually disabled. ### What is the expected behavior Only one notification appears after the torrent finishes downloading. There should be at least an option to disable the "Finished moving" notification. ### Steps to reproduce Download any torrent. ### Extra info(if any) (type here)
deekerman 2026-02-21 21:09:33 -05:00
  • closed this issue
  • added the
    GUI
    label
Author
Owner

@randomish commented on GitHub (Nov 12, 2020):

Agree with the OP. I guess this started in v4.3.0 due to this from the changelog:
"FEATURE: Notify user when torrent moving finished (glassez)"

I don't see the point of this since it only results in double notifications every time a torrent finishes and it's moved from whichever temp folder you have configured to the finished folder.

If there is some case where this feature is actually useful, there should at least be an option to turn it off, and it should probably be disabled by default.

@randomish commented on GitHub (Nov 12, 2020): Agree with the OP. I guess this started in v4.3.0 due to this from the changelog: "FEATURE: Notify user when torrent moving finished (glassez)" I don't see the point of this since it only results in double notifications every time a torrent finishes and it's moved from whichever temp folder you have configured to the finished folder. If there is some case where this feature is actually useful, there should at least be an option to turn it off, and it should probably be disabled by default.
Author
Owner

@Donatzsky commented on GitHub (Nov 13, 2020):

Yes, this is super annoying.
Being told that a torrent has been moved is, for most users, going to be totally irrelevant.

There's a related issue here: #13100

@Donatzsky commented on GitHub (Nov 13, 2020): Yes, this is super annoying. Being told that a torrent has been moved is, for most users, going to be totally irrelevant. There's a related issue here: #13100
Author
Owner

@FranciscoPombal commented on GitHub (Nov 29, 2020):

@glassez ping.

@FranciscoPombal commented on GitHub (Nov 29, 2020): @glassez ping.
Author
Owner

@glassez commented on GitHub (Nov 30, 2020):

Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")?

@glassez commented on GitHub (Nov 30, 2020): Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")?
Author
Owner

@thalieht commented on GitHub (Nov 30, 2020):

Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")?

Yes IMO.

@thalieht commented on GitHub (Nov 30, 2020): >Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")? Yes IMO.
Author
Owner

@GeorgeSpelvin commented on GitHub (Dec 20, 2020):

Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")?

A "very yes" from me, too. One normal notification for normal torrents and (an optional?) one for those set for special locations.

@GeorgeSpelvin commented on GitHub (Dec 20, 2020): > Should I leave notifications only for torrents that are explicitly moved by the user (e.g. via "Set location")? A "very yes" from me, too. One normal notification for normal torrents and (an optional?) one for those set for special locations.
Author
Owner

@biglui commented on GitHub (Dec 26, 2020):

Even for those of us who manually set a torrent to move will find this annoying because it will followed immediately by the torrent completion notification. There is no point in sending this notification when completion notification meant it has been moved. It may be useful if you set the notification when it starts to move because some moves may take a minute or two to complete for larger files, and during the move, your system performance may degrade.

@biglui commented on GitHub (Dec 26, 2020): Even for those of us who manually set a torrent to move will find this annoying because it will followed immediately by the torrent completion notification. There is no point in sending this notification when completion notification meant it has been moved. It *may* be useful if you set the notification when it *starts* to move because some moves may take a minute or two to complete for larger files, and during the move, your system performance may degrade.
Author
Owner

@glassez commented on GitHub (Dec 31, 2020):

I am more and more inclined to the idea of completely removing notifications about moving files. Unfortunately, I can't think of any compromise option that would not be boring in the general case.

@glassez commented on GitHub (Dec 31, 2020): I am more and more inclined to the idea of completely removing notifications about moving files. Unfortunately, I can't think of any compromise option that would not be boring in the general case.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#11112
No description provided.