mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
ERROR - Movie file and Force Recheck file, no there is no indicator #17118
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @l-n0-0b on GitHub (Aug 27, 2025).
Suggestion
v5.1.2
Arch Linux (Flatpak)
Xorg11
The theme from the system and custom icons are disabled.
Use case
When selecting several lines, for example 4, the movement indicator does not show (and sometimes checks, too).
There is a limit of 2 - for verification.
Is it possible to equate the limitation of the number of checks to the number of movements?
It's even worse when queues are enabled.
Why not move all the selected ones at once?
Extra info/examples/attachments
No response
@thalieht commented on GitHub (Aug 27, 2025):
I don't understand either of your issues (the other #23171).
@luzpaz commented on GitHub (Aug 27, 2025):
@l-n0-0b very difficult to understand this ticket. It needs screenshots and more elaboration.
@l-n0-0b commented on GitHub (Aug 27, 2025):
Are there no synonyms in English? (words similar in meaning). Why did everyone suddenly stop understanding?
You don't understand what is in your program's interface and where, so as not to guess?
Good. I'm spelling out the names. "Table - right mouse button" - "Force Recheck".
Sometimes the "Force Recheck" progress bar is not displayed - 1% -100%...
I have "Maximum active checking - (2)" in my settings.
And there is also "Table - right mouse button" - ""Set location"".
The progress bar (movement) of 1%-100% is also not displayed.
Is it possible to add a "Maximum ""Set location"" - (2)"" when moving, so that with a large number of allocations, it is done one at a time so as not to create an increased load on the disk - and everything does not freeze stop programs.
It's impossible to spend so much time moving one piece at a time.
@thalieht commented on GitHub (Aug 28, 2025):
Can't reproduce.
Not implemented. See #508
There's supposed to be a moving queue with one torrent at a time being moved but i don't know how to test it. Maybe you just saw "Moving" status on your torrents and you assumed they're all moving simultaneously?
@l-n0-0b commented on GitHub (Aug 28, 2025):
It happens rarely, but aptly. Especially if you add a check one at a time, you have to repeat it a lot. At some point, it stops doing or showing. This is especially true when a check is already running, or a lot of checks are running, or there are a lot of downloads. There is nothing written about this in the log (in the interface).
Yes, everyone is moving in the list. What I saw in the program is what I'm saying, do they move one at a time? Because if you select a lot at once (or select one after the other) - by braking and eventually by freezing the program - it feels like everyone is moving at once (maybe you can set this up somewhere?) So, I ran it on 2 different disks at once, both under 100% load.
@l-n0-0b commented on GitHub (Aug 30, 2025):
It down and moves at the same time.
And this, how does it happen?
@l-n0-0b commented on GitHub (Aug 30, 2025):
I ran it through the terminal and there are these lines, but I do not know at what point they came - there is no indication of the time.
@l-n0-0b commented on GitHub (Sep 2, 2025):
but qbit can't do more than literally 1-2 tasks with files.
As a result, the NTFS file system is not particularly related to the problem.