Completed torrents get paused rather than checked #7743

Closed
opened 2026-02-21 19:08:44 -05:00 by deekerman · 1 comment
Owner

Originally created by @Nerva72 on GitHub (Sep 13, 2018).

Please provide the following information

qBittorrent version and Operating System

qBittorrent 4.1.2 x64 (and many previous versions) and Windows 7 x64

If on linux, libtorrent and Qt version

(type here)

What is the problem

When a torrent completes, qBittorrent checks it, but if another torrent completes while the first one is being checked, the second torrent is "paused" rather than "checking", so when the first torrent completes checking, the second torrent stays paused rather than being checked next.

What is the expected behavior

If a second torrent completes while another torrent is being checked, the second torrent should be put in the checking queue and given the "checking" status.

Steps to reproduce

(type here)

Extra info(if any)

(type here)

Originally created by @Nerva72 on GitHub (Sep 13, 2018). **Please provide the following information** ### qBittorrent version and Operating System qBittorrent 4.1.2 x64 (and many previous versions) and Windows 7 x64 ### If on linux, libtorrent and Qt version (type here) ### What is the problem When a torrent completes, qBittorrent checks it, but if another torrent completes while the first one is being checked, the second torrent is "paused" rather than "checking", so when the first torrent completes checking, the second torrent stays paused rather than being checked next. ### What is the expected behavior If a second torrent completes while another torrent is being checked, the second torrent should be put in the checking queue and given the "checking" status. ### Steps to reproduce (type here) ### Extra info(if any) (type here)
deekerman 2026-02-21 19:08:44 -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.
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#7743
No description provided.