Upstream have closed their bug since 1.0.7 is outdated. Does the problem still exist with deluge 1.1.2.dfsg-1 ?
Upstream have closed their bug since 1.0.7 is outdated. Does the problem still exist with deluge 1.1.2.dfsg-1 ?