starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Added on date changes on restart #3437

New issue

Closed

opened 2026-02-21 16:46:20 -05:00 by deekerman · 10 comments

deekerman commented

2026-02-21 16:46:20 -05:00

Owner

Originally created by @Trueffel on GitHub (Dec 2, 2015).

After the update to 3.3 (win7 64bit) some torrents I've added a few days ago (since then), appear to be re-added on client restart as they're listed with the exact date and time of the last restart and get changed on every new start.

Originally created by @Trueffel on GitHub (Dec 2, 2015). After the update to 3.3 (win7 64bit) some torrents I've added a few days ago (since then), appear to be re-added on client restart as they're listed with the exact date and time of the last restart and get changed on every new start.

deekerman closed this issue

2026-02-21 16:46:23 -05:00

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@GaradaK7 commented on GitHub (Dec 28, 2015):

Same bug here.
WIndows 8.1 64bits, qBittorrent 3.3.1
Seems that the torrents that change the date/time on every run are magnet-links. Torrents added as files aren't affected.

@GaradaK7 commented on GitHub (Dec 28, 2015): Same bug here. WIndows 8.1 64bits, qBittorrent 3.3.1 Seems that the torrents that change the date/time on every run are magnet-links. Torrents added as files aren't affected.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@beneficadoramocaba commented on GitHub (Feb 15, 2017):

Still exists.

@beneficadoramocaba commented on GitHub (Feb 15, 2017): Still exists.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@Alonshow commented on GitHub (Sep 1, 2017):

Still happening in 3.3.15. Anybody checking this?

@Alonshow commented on GitHub (Sep 1, 2017): Still happening in 3.3.15. Anybody checking this?

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@Fyren commented on GitHub (May 7, 2018):

I'm experiencing this with 4.1.0. The torrents with the reset "added on" field are magnet links, as also stated in an earlier comment on this issue.

@Fyren commented on GitHub (May 7, 2018): I'm experiencing this with 4.1.0. The torrents with the reset "added on" field are magnet links, as also stated in an earlier comment on this issue.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@Chocobo1 commented on GitHub (May 7, 2018):

This seems to happen only when the magnet's metadata is not retrieved.

@Chocobo1 commented on GitHub (May 7, 2018): This seems to happen only when the magnet's metadata is not retrieved.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@beneficadoramocaba commented on GitHub (May 7, 2018):

The timestamp is created when the magnet metadata is retrieved. qBittorrent does not retrieve magnet metadata until you begin the download. Therefore magnet links which are added in a "Paused" state don't show the correct date. See #929, #6389, etc.

@beneficadoramocaba commented on GitHub (May 7, 2018): The timestamp is created when the magnet metadata is retrieved. qBittorrent does not retrieve magnet metadata until you begin the download. Therefore magnet links which are added in a "Paused" state don't show the correct date. See #929, #6389, etc.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@Trueffel commented on GitHub (May 9, 2018):

Thanks, guess this can be closed then

@Trueffel commented on GitHub (May 9, 2018): Thanks, guess this can be closed then

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@Fyren commented on GitHub (May 9, 2018):

I'd still call it a bug even if there's an explanation as to why it happens. The metadata mentioned is intrinsic to the torrent, but the added on data is not.

@Fyren commented on GitHub (May 9, 2018): I'd still call it a bug even if there's an explanation as to why it happens. The metadata mentioned is intrinsic to the torrent, but the added on data is not.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@beneficadoramocaba commented on GitHub (May 10, 2018):

There is a workaround, but it is fairly convoluted as the software needed is not available from the author in a compiled format. I meant to post the method over on #929 but (excuses). I am putting it on my to-do list for the next week or so, which is likely sooner than it will be fixed in the application itself, so you may want to subscribe to that.

@beneficadoramocaba commented on GitHub (May 10, 2018): There is a workaround, but it is fairly convoluted as the software needed is not available from the author in a compiled format. I meant to post the method over on #929 but (excuses). I am putting it on my to-do list for the next week or so, which is likely sooner than it will be fixed in the application itself, so you may want to subscribe to that.

deekerman commented

2026-02-21 16:46:25 -05:00

Author

Owner

@beneficadoramocaba commented on GitHub (May 21, 2018):

Solution is now posted.

@beneficadoramocaba commented on GitHub (May 21, 2018): Solution is now posted.