mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qbittorrent-2.9.7 broken torrent-check function in import procedure #49
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#49
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 @ssten on GitHub (Aug 25, 2012).
I've moved fetched data to my custom directory.
And want to start seeding the fetched torrent (import function).
But when I've done so, I've discovered, that qbittorrent again starts torrent downloading.
Exploreing the issue showed, that executed after import torrent check function doesn't works.
Executing force recheck command from main menu solved issue, so I can seed previously fetched torrent.
In addition, I think that auto-start downloading at adding torrent-index is not the best choice for default settings (see the reported issue).
P.S. GNU/Linux, now 3.4.9. amd64 arch.
@azcohen commented on GitHub (Sep 21, 2012):
I'm experiencing the same problem under Linux 2.6.25, except the force recheck doesn't help, it just says checking, then queuing, then stalled..
@sledgehammer999 commented on GitHub (Oct 1, 2013):
This is fixed in the 3.0.x series, can't remember exact version.