minor percentage issue

[lvm]

Single-file torrent, download percentage on the 'files' tab should be the same as the percentage of the whole torrent in the torrent list, but in reality it is always slightly behind. If I am to believe the 'details' tab the correct figure is in the master torrent list.

[Ubugenko]

Quite the same problem here, but it is not a minor issue, it is more a major problem to me with deluge 5.8.9 with hardy !
For example, at the moment, I have a 5.2 Go multiple-files-torrent (25 x 210 Mo approximatively) to download : General percentage is showing something like 60 % done, while percentage per files hardly show 5 or 8 % per file !
Problem is I often need to setup highest priority for some files, then add the other files to download as I finish the first ones. I can't do that anymore at the moment as Deluge can't show me the real state of the currently downloding files ...

[fxyefx]

This is a pretty bad problem
I've had to resort to using transmission or ktorrent (depending on my mood) because of how much downloaded-but-not-yet-completed data I've lost:
viewtopic.php?f=7&t=4115

[Ubugenko]

Strange, i was thinking that issue was resolved with version 0.5.9.3, but it shows up again. I'm beginning to be tired of it, since I can't know for sure when a file is over or not. Do you guys still experiencing the problem ?

[aninhumer]

There will always be a slight difference between the overall completion and file completion percentage, because the file completion only shows the percentage of blocks completed, whereas overall includes all data, including unchecked.
However as some people have been stating, in 0.5.9.2 and .3, deluge has not been completing blocks normally, resulting in this discrepancy increasing, but more importantly, leading to MAJOR loss of data on a recheck. It also makes seeding initially difficult, as you cannot seed until you complete at least one block.

I have rolled back to 0.5.9.1 and it does not seem to be a problem anymore. Additionally any data downloaded in 0.5.9.2 seems to be saved properly so I didn't lose too much data.
Someone here also said this was happening to them in 0.5.8.9? I don't know what that means, but if it's true it should probably be added to the bug report.

I made a post about it here: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=7055
And there is a similar problem reported here: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=7155

I have submitted a bug report here: http://dev.deluge-torrent.org/ticket/295

I would kind of appreciate it if we could get a dev response about this issue somewhere?