Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Force recheck not working : Linux (links to similar Windows and WebUI issues) #10668
Please provide the following information
qBittorrent version and Operating System
Version 4.1.5 64 Bit
If on linux, libtorrent and Qt version
What is the problem
with complete downloads
Force Recheck simply does not work. At all.
with complete downloads, listed as 0% in qbittorrent
What is the expected behavior
The downloaded files are rechecked.
Steps to reproduce
Try "force recheck" on any downloaded files.
Extra info(if any)
The files are stored on removeable media (1TB drive accessed over usb, mounted by udev). I can't see any mounting, unmounting problems.
Similar bugs, via the WebUI and on Windows:
Separate issue. If qBittorrent is expecting part files (*.!qB files) from a torrent you added, you will have to rename the completed files that you import to the download directory to have the .!qB extension. Or disable part files in QBT settings before adding the torrent / magnet.
In the recheck department, 4.1.6 just stopped rechecking torrents in parallel.
Please share if you use any of these or a combination of them so i can try to reproduce and if successful, look around the code.
I will agree that there are still bugs with recheck. As I stated above, and thalieht eluded to, QBT has difficulty discovering complete files depending on several different states of the client configuration and the torrent's completeness. QBT does not perform a very exhaustive search of complete files where one might expect to find completed files, so they end up not being recheck-able in the torrent's current [inaccurately incomplete] state.
QBT should do more to discover completed files in the myriad of plausible locations. Eg: Within the temp location, within the completed downloads location, within a folder, the category destination, .unwanted folders, with and without the .!qB part extension.
In my case:
@AbsurdMagpieScrutinies i can't reproduce :(
I'm not saying there isn't a problem, maybe it's some other setting i can't think of...