If you set an (inactive) seed time for a single torrent, it get's set down to 525,600 min. (1 year) #16414

New issue

Closed

opened 2026-02-22 03:06:05 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 03:06:05 -05:00

Owner

Originally created by @Heinz14 on GitHub (Dec 4, 2024).

qBittorrent & operating system versions

qBittorrent: 5.0.2 x64
Operating system: Windows 10 Pro x64 (22H2) 10.0.19045.5011
Qt: 6.7.3
libtorrent-rasterbar: 1.2.19

What is the problem?

The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years).

Steps to reproduce

Set a maximum seed time or maximum inactive seeding time for a single torrent to anything above 525,600 min.
It'll get set down automatically to 525,600 min. (1 year).

Additional context

No response

Log(s) & preferences file(s)

qbittorrent.log

Originally created by @Heinz14 on GitHub (Dec 4, 2024). ### qBittorrent & operating system versions qBittorrent: 5.0.2 x64 Operating system: Windows 10 Pro x64 (22H2) 10.0.19045.5011 Qt: 6.7.3 libtorrent-rasterbar: 1.2.19 ### What is the problem? The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years). ### Steps to reproduce 1. Set a maximum seed time or maximum inactive seeding time for a single torrent to anything above 525,600 min. 2. It'll get set down automatically to 525,600 min. (1 year). ### Additional context _No response_ ### Log(s) & preferences file(s) [qbittorrent.log](https://github.com/user-attachments/files/18009738/qbittorrent.log)

deekerman

2026-02-22 03:06:05 -05:00

closed this issue
added the
GUI
label

deekerman commented

2026-02-22 03:06:17 -05:00

Author

Owner

@thalieht commented on GitHub (Dec 4, 2024):

The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years).

The general seed time limit is also 525.600 min internally. The GUI spinbox doesn't show the real value if it's higher than that.

@thalieht commented on GitHub (Dec 4, 2024): >The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years). The general seed time limit is also 525.600 min _internally_. The GUI spinbox doesn't show the real value if it's higher than that.

deekerman commented

2026-02-22 03:06:17 -05:00

Author

Owner

@Heinz14 commented on GitHub (Dec 4, 2024):

The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years).

The general seed time limit is also 525.600 min internally. The GUI spinbox doesn't show the real value if it's higher than that.

Why is the seed time restricted that low?
Then it's a bug in the general seed time, because there it's shown till 9,999,999 min, even after saving and reopening the window.

@Heinz14 commented on GitHub (Dec 4, 2024): > > The seed time for a single torrent is far more restricted (525,600 min. (1 year)) than the general seed time limit (9,999,999 min. / about 19 years). > > The general seed time limit is also 525.600 min _internally_. The GUI spinbox doesn't show the real value if it's higher than that. 1. Why is the seed time restricted that low? 2. Then it's a bug in the general seed time, because there it's shown till 9,999,999 min, even after saving and reopening the window.

deekerman commented

2026-02-22 03:06:17 -05:00

Author

Owner

@thalieht commented on GitHub (Dec 4, 2024):

Why is the seed time restricted that low?

Arbitrary choice i guess and personally i wouldn't call 1 year "low" (why use a limit at all if you want more).

Then it's a bug in the general seed time, because there it's shown till 9,999,999 min, even after saving and reopening the window.

Yep.

@thalieht commented on GitHub (Dec 4, 2024): >1. Why is the seed time restricted that low? Arbitrary choice i guess and personally i wouldn't call 1 year "low" (why use a limit at all if you want more). >2. Then it's a bug in the general seed time, because there it's shown till 9,999,999 min, even after saving and reopening the window. Yep.