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 769761 - Deleting files with "Permanently Delete" option makes Nautilus status indicator show huge negative number
Deleting files with "Permanently Delete" option makes Nautilus status indicat...
Status: RESOLVED DUPLICATE of bug 759703
Product: nautilus
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-08-11 18:31 UTC by Inactive account
Modified: 2017-08-24 14:55 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20


Description Inactive account 2016-08-11 18:31:45 UTC 
I was using the "Permanently Delete" option in Nautilus to delete a folder which was about 1.7GB in size and the most strange thing happened during the deletion:

    https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1612376/+attachment/4719275/+files/Negative_Amount_Of_Files_Deleted_Per_Second_Nautilus.png

The number kept changing from a huge negative number, to a positive number half the size, but still unrealistic in terms of size and the amount of files actually in the folder which was in the 100,000s, not the 100,000,000s or similar as it often showed. I am running Ubuntu GNOME 16.04 with GNOME 3.20. The deletion appeared successful, but I still thought I should report the odd statistics.

I initially filed a report on the matter here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1612376 But thought I should also do so upstream.
Comment 1 António Fernandes 2017-08-24 14:55:01 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 759703 ***