Guys, I've just hit an easily replicable bug with 0.5.8.7 (running under FreeBSD 7) force recheck. When there is a recheck already in progress and user selects another 'force recheck' on the same torrent, that torrent is instantly removed from the list. First I thought it's just some out-of-index display problem with the list (yes, I was a Windows developer once), but restarting Deluge doesn't help, the torrent is gone.
Of course, one should normally not need to multiply select force recheck on the same file, though I've hit it when scheduling a few torrents for recheck and accidentally clicked the same one twice. So you see, this can happen from time to time :)
0.5.8.7 force recheck bug
Re: 0.5.8.7 force recheck bug
i may have found a fix. well, at least it works for me 
after you add all the torrents in deluge, go to your home folder, look at hiddin folders and go to .config/deluge/torrentfiles ... select all the files there (not the folder), right click, select propreties and allow read and write for everyone under the Permissions tab. No torrents rechecking for me after i did that.

after you add all the torrents in deluge, go to your home folder, look at hiddin folders and go to .config/deluge/torrentfiles ... select all the files there (not the folder), right click, select propreties and allow read and write for everyone under the Permissions tab. No torrents rechecking for me after i did that.
Re: 0.5.8.7 force recheck bug
Bug report:
using win ver-
When I hit recheck, my ratio changes dramatically-it goes to shutting off seeding.
Additional info-
I am not using the default folders for any of the save operations.
I move completed downloads and torrent files to separate folders.
Perhaps that is why this happens???
using win ver-
When I hit recheck, my ratio changes dramatically-it goes to shutting off seeding.
Additional info-
I am not using the default folders for any of the save operations.
I move completed downloads and torrent files to separate folders.
Perhaps that is why this happens???