mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
ETA stuck, ignoring seed limits #12553
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#12553
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 @Timofiev on GitHub (Nov 5, 2021).
qBittorrent & operating system versions
qBittorrent: 4.3.8
Operating system: TrueNAS-12.0-U6
What is the problem?
After finish downloading some of my torrents show the maximum ETA for seeding, completely ignoring the seeding limits I set.
After changing my seeding limits, the ETA becoming equal with the seeding limit time I set.
These torrents continue to seed even after the seeding limit expire. All other torrents working properly and I don't know whats the issue.
Steps to reproduce
I have no idea. It seems random.
Additional context
The seeding limit is:
ratio: 1
time: 3000 min (2d 2h)
Log(s) & preferences file(s)
No response
@thalieht commented on GitHub (Nov 5, 2021):
Duplicate of #10223
This happens to torrents with excluded files.
@Timofiev commented on GitHub (Nov 6, 2021):
Oh sorry to duplicate a bug which exists since 2019 Jan. Maybe it's a bug that become an intended function who knows. Worth registrating to report a completely working and intended fuction.