"Last Seen Complete" is not consistent or accurate #11564

New issue

Closed

opened 2026-02-21 21:40:05 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-21 21:40:05 -05:00

Owner

Originally created by @Knocks on GitHub (Jan 6, 2021).

The Last Seen Complete date sometimes disappears for some torrents after restarting qBittorrent or after connecting to another VPN server. Torrents that were connected to seeds and seen complete before no longer have a "last seen complete" date.

Also, sometimes that field shows a value that doesn't make sense. For example, a torrent that was added in January 2021 will show a last seen complete date of August 2020. I thought that field was supposed to show the last time your client has seen the torrent complete, not the last time the tracker has seen it complete. Does the tracker even convey that information to clients?

qBittorrent version and Operating System

4.3.2

Originally created by @Knocks on GitHub (Jan 6, 2021). The Last Seen Complete date sometimes disappears for some torrents after restarting qBittorrent or after connecting to another VPN server. Torrents that were connected to seeds and seen complete before no longer have a "last seen complete" date. Also, sometimes that field shows a value that doesn't make sense. For example, a torrent that was added in January 2021 will show a last seen complete date of August 2020. I thought that field was supposed to show the last time **your** client has seen the torrent complete, not the last time the tracker has seen it complete. Does the tracker even convey that information to clients? ### qBittorrent version and Operating System 4.3.2

deekerman

2026-02-21 21:40:05 -05:00

closed this issue
added the
Core
label

deekerman commented

2026-02-21 21:40:19 -05:00

Author

Owner

@jagannatharjun commented on GitHub (Jan 6, 2021):

@Knocks IMO the problem is even worse. do you use private trackers? Can you compare the download and upload data between the private tracker and what qbittorrent show. In my case, I downloaded a torrent in many steps (in terms of file) on the private tracker, torrent shows 19.5 uploads and 36.21 downloads but qbittorent only shows 10.55 upload and 24.48 download. Can anybody else confirm this?

@jagannatharjun commented on GitHub (Jan 6, 2021): @Knocks IMO the problem is even worse. do you use private trackers? Can you compare the download and upload data between the private tracker and what qbittorrent show. In my case, I downloaded a torrent in many steps (in terms of file) on the private tracker, torrent shows 19.5 uploads and 36.21 downloads but qbittorent only shows 10.55 upload and 24.48 download. Can anybody else confirm this?

deekerman commented

2026-02-21 21:40:21 -05:00

Author

Owner

@Knocks commented on GitHub (Jan 6, 2021):

Also, sometimes qBittorrent shows that I am connected to a seed (or several seeds), but the download never begins and "last seen complete" is not updated to "now." That by definition is wrong. Being connected to a seed means the torrent has already been seen as complete.

Either qBittorrent is falsely reporting that you are connected to a seed or its incorrectly reporting when the torrent was seen complete.

@Knocks commented on GitHub (Jan 6, 2021): Also, sometimes qBittorrent shows that I am connected to a seed (or several seeds), but the download never begins and "last seen complete" is not updated to "now." That by definition is wrong. Being connected to a seed means the torrent has already been seen as complete. Either qBittorrent is falsely reporting that you are connected to a seed or its incorrectly reporting when the torrent was seen complete.

deekerman commented

2026-02-21 21:40:21 -05:00

Author

Owner

@Dobbelklick commented on GitHub (May 3, 2021):

My friend has probably related problems with the "Last seen" date where apparently the month and date got swapped. Here is a screenshot of a friends torrent client:

Take a look at the "Date added" column. It doesn't make sense.

@Dobbelklick commented on GitHub (May 3, 2021): My friend has probably related problems with the "Last seen" date where apparently the month and date got swapped. Here is a screenshot of a friends torrent client: ![image](https://user-images.githubusercontent.com/12908506/116868746-a3f28900-ac0f-11eb-8b6e-5dbb6c7aa4c7.png) Take a look at the "Date added" column. It doesn't make sense.

deekerman commented

2026-02-21 21:40:21 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 19, 2025):

This ticket has been closed.

Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.

If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.
A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Thank you for your contribution(s).

@xavier2k6 commented on GitHub (Mar 19, 2025): ### This ticket has been closed. ____ **Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.** ____ * If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. * Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. * Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. * A new issue report with relevant updated data gathered from the **latest** version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. * Thank you for your contribution(s).