Opened 4 years ago
Closed 3 years ago
#3458 closed bug (Upstream)
"move completed to" doesn't work
Reported by: | MotoFckr9k | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | needs verified |
Component: | libtorrent | Version: | 2.0.3 |
Keywords: | move_storage | Cc: | imagenoir@gmail.com |
Description
When a torrent finishes, it doesn't get moved to the "completed" path anymore. This worked fine at some point. Pretty sure it worked fine before in this same version. The path is writable and the log doesn't say anything.
Change History (8)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
This is a libtorrent bug. Possibly fixed in 1.2.11 https://github.com/arvidn/libtorrent/releases
It didn't work for me with libtorrent 1.2.9(Debian Bullseye).
With version 1.2.12 it worked.
comment:5 by , 4 years ago
Cc: | added |
---|
comment:6 by , 4 years ago
Component: | Unknown → libtorrent |
---|---|
Keywords: | move_storage added |
comment:7 by , 3 years ago
Issue is fixed in Debian Buster and Debian Bullseye. A maintainer incuded the upstream patch that apparently fixes the issue.
comment:8 by , 3 years ago
Resolution: | → Upstream |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It turns out that this doesn't happen to every torrent. I started two and only one of them got moved.