After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 460730 - directory dimension not updated after a move
directory dimension not updated after a move
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-26 20:06 UTC by Sebastien Bacher
Modified: 2021-06-18 15:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Sebastien Bacher 2007-07-26 20:06:52 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/125453

"Binary package hint: nautilus

nautilus 2.19.4-0ubuntu2

you can set in preferences, visualization, to add the "dimension" shown under a file/directory
this means filesize for files, and number of elements for a directoty.

do this simple think from ma nautilus window: create two directories:
source destination
create some files in source, and cut them
go to the parent directory:
you can see that source has now the wanted dimension (e.g. 3 files)
now paste, right clicking paste on the destination directory (not going into it), and you will see that the destination directory has the right dimension, but the source directory still has the previous dimension!

the source dimension should be updated when moving files

If you do the same thing from a shell using mv, and you keep open the parent folder, the result is the opposite:
the source directory count is updated, while the destination count is not updated.

After doing other tests with touch and rm, I see that the problem persists. Maybe inotify is not used well, when displaying the dimension?"
Comment 1 Cosimo Cecchi 2008-02-08 11:30:30 UTC
Confirming, this still happens with 2.21.
Comment 2 Nicolò Chieffo 2009-06-16 08:58:38 UTC
Do any of you know what's the problem?
If it's not fixable, it should be workarounded by removing file count
Comment 3 André Klapper 2021-06-18 15:13:41 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.