GNOME Bugzilla – Bug 99034
wrong files' count while copying/deleting/moving files
Last modified: 2006-04-26 08:30:40 UTC
When copying a bunch of files (actually, using ssh://), the Files copied XX of YY display shows the wrong YY. Either that, or the rightmost digits are getting chopped off. I figured this out when I was on file "4 of 2" ;-).
this reminded of bug 99848
Seems to work fine with nautilus 2.4. Could you test with it to say if the bug is still here on your box ? Thanks
*** Bug 127859 has been marked as a duplicate of this bug. ***
According to 127859 still here with nautilus 2.4
Sorry for missing the 11/22 e-mail. Yes, this is still an active problem in the 2.4 distributed w/ Fedora Core 1.
do you still have the problem with nautilus 2.8 ? Do you have a small test case to get it ?
still here with 2.9 in fact. From #162664: "This bug has been opened here: https://bugzilla.ubuntu.com/5110 When I copy directory *and* several aditional items with it, directory items doesn't count in and it appears like overload of ftp copying (getting 10 out 3 items, for example)."
*** Bug 162664 has been marked as a duplicate of this bug. ***
*** Bug 139469 has been marked as a duplicate of this bug. ***
(Comment from 139469): I see four ways of resolving this: - Index all folders before deleting (insane) - Count only direct subfolders and -files - Increase count of all objects as new objects are seen (confusing for users) - Don't show the "of ..." thingie at all Any opinions?
I suggest stick with two of Christian suggestions: * Count only direct subfolders and files - it would good enough, I don't need to know count of all objects, I just need to see some kind of progress. Or if it is hard to achieve, then don't show the 'of ..' thingie at all, however, it could be confusing.
Created attachment 54476 [details] Moving files: look at file count and time remaining
I am running Nautilus 2.12.1 (on Ubuntu.)
I want to point out that this problem is solved in Ubuntu Drapper, using Nautilus 2.13.91 and gnome-vfs 2.13.91. Counting is correct and timer is updated correctly. So I suggest close this bug.
I'm assured that this has been fixed, please reopen if not.