I can not find other evidence (it seems incredible because I seem to remember the same problem many, many years ago), but meeting the same mistake common to all Linux distributions (including old), install or liveCD, both on real machines that virtualized (even different hardware). Example: If you select all folders (ctrl+a) in the root and requesting the property, the result is more than 128TB, or much greater than the actual space of a small HD etc.. Perhaps the problem stems from some overflows because there is an exception: asking the space occupied of all folders in a DVD installation where there is a link to the folder containing most of the packages (Example: debian DVD), dolphin returns the space occupied properly. Nautilus may initially give the correct number and then double it. Lubuntu is rather special, says: total file 1Gb, 4GB of disk space. Insisting repeatedly turns: total files 4 GB, 8GB disk space.
Thanks for the report, but please note that not only different devices, but also lots of stuff (like, e.g., /proc) that can't even be considered a file is mounted in /. Therefore, you cannot expect to get a reasonable result if you check the space occupied by /. I'm pretty sure that this has been reported earlier, but I couldn't find the old report.
OK. But in blissful ignorance of the data structure: I've always found illogical mount a disk into another disk. Personally I would prefer mont in ramdisk or whatever. At least the system should be aware of this, and provide separate data and consistent for each unit, and ignore false and misleading. (having digits in base ten guess it heresy to talk about, right?) I found many other things inconsistent and / or problems, but I do not know who to talk to and if you mention it as a bug or if you define "features". For example, the system hangs when RAM and swap runs out, without any warning message. Or do not hibernate because swap is small or non-free. Incredible. (it is essential to an emergency system: a temporary file written wherever there is space)
There's an earlier report about this, I'll mark your report as a duplicate (note that it is assigned to kdelibs - the Properties dialog is not part of Dolphin itself). (In reply to comment #2) > OK. But in blissful ignorance of the data structure: I've always found > illogical mount a disk into another disk. Personally I would prefer mont in > ramdisk or whatever. At least the system should be aware of this, and > provide separate data and consistent for each unit, and ignore false and > misleading. (having digits in base ten guess it heresy to talk about, right?) It might be possible to ignore /proc and other non-files for the size calculation, but the drives which are mounted in subdirectories of / cannot just be ignored when you ask for the size of everything in /. Linux just works like that, if you like it or not. But let us please not discuss that here, this has nothing to do with Dolphin or KDE, and we cannot do anything about it anyway. > I found many other things inconsistent and / or problems, but I do not know > who to talk to and if you mention it as a bug or if you define "features". > For example, the system hangs when RAM and swap runs out, without any > warning message. Or do not hibernate because swap is small or non-free. > Incredible. (it is essential to an emergency system: a temporary file > written wherever there is space) I think you can configure the kernel to store the hibernation data in a file on some partition, rather than on a separate swap partition. But note that these things have nothing to do with Dolphin. Please try to stay on-topic here, everything else is just a waste of time. Thanks for your understanding. *** This bug has been marked as a duplicate of bug 298133 ***
I know that some topics are not related to dolphin, wondering just where and with whom to talk. I have not found anything like a wish list, I missed? Can you help me? (I tried it on openFATE, but I see it difficult to understand each other, it will unfortunately because of my bad English). Infinite apologies. In fact it has already been reported that /proc/kcore results from 128TiB and I have read concerning the maximum RAM that can be allocated from the 64bit system. But I hope not to be the only one who likes to see things neat and consistent, so I propose the following in dolphin: 1) To solve the above problem could disable the "Standard Properties" for the root of all disks (at least the system disk) and replaced it with some library partitioning programs to provide details in the best way (give an impression more professional program). I hope that this is possible without waiting too long, possibly without the pie chart. :) 2) It is useful to view (perhaps with a label mobile) node connecting the various disk / partition because it may happen to have the same size and without a proper name. 3) To be able to perform the copy of the text in the result window.
> I have not found anything like a wish list, I missed? You can just file a report at bugs.kde.org with the severity 'wishlist'. However, please consider that what you suggest (at least point 1, I didn't quite get what 2 and 3 are about) is way outside the scope of Dolphin. Moreover, just filing a report will have very little effect - somebody would have to volunteer to implement something like that.