GNOME Bugzilla – Bug 782444
Can not calculate the disk size of multiple files and folders selected at once
Last modified: 2017-05-10 15:33:43 UTC
Although specified as 3.24, the bug is there from the very first day of GNOME 3. To reproduce it; - open nautilus and navigate to a folder with multiple folders and files in it, it may be an external drive, a root folder, a local folder, even a remote folder. The format won't matter, either. NTFS, EXT4, ExFAT etc. all will have the bug. (if the target folder is smaller than 200mb, it is likely that the bug will not appear, so pick a big folder please!!) - Select some folders and files (not necessarily all of them) and right click, choose "properties". - There, you will see that the total size of the selected items can not be calculated. The counting indicator and the numbers will repeat counting, go back to zero and never stop, nor will allow you to see the result. Some may think; going one folder up and seeing the size of the main directory would help it but it won't do any good when I need only some specific files and folders selected at once (not all of them). This is very useful when you are moving hundreds of photos and videos from local to external drives (or vice versa) and checking which folders are done, which are not. Doing the measurement one by one for each folder is not an option when there are hundreds of folders. BTW, this bug is really there for 7 years nearly! Since then, Nautilus reincarnated many times as design and function-wise. It is sad to see this bug remains till this day.
*** This bug has been marked as a duplicate of bug 755483 ***
It’s a bit hard to fix it, since no one has been able to provide reliable steps to reproduce the issue. I’ve had luck with symlinks, but apparently that’s not the whole story.
I would like to help, if you walk me through the steps to crate a useful data (I don't even know what a symlink is). If what's needed is not a technical data (like a logcat), a clear show of the bug instead; I can make video of the bug and link it here?
(In reply to Can from comment #3) > I would like to help, if you walk me through the steps to crate a useful > data (I don't even know what a symlink is). > > If what's needed is not a technical data (like a logcat), a clear show of > the bug instead; I can make video of the bug and link it here? Having a minimal set of files that trigger the bug would be ideal. One other reporter tried generating a bunch of files to achieve that, but I don’t think we got anywhere. In any case, I don’t really know what the exact steps would be, but I’ll try to allocate some time this week to give this another whirl.