desktop-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/799601

Title:
  Nautilus should clearly indicate that a long-running large-data file
  copy is progressing

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus

  If copying a large amount of data on a relatively slow network
  connection, it's impossible to see whether the copy is actually
  working or has frozen. For example, showing "17.2GB of 30GB copied
  (220k/sec), estimated time remaining 18 hours". If that copy process
  freezes, or the network drops out, it's almost impossible to tell that
  it's done so; the 17.2GB will eventually change to 17.3GB, but you
  have to watch the thing for 5-10 minutes to see that change. The
  progress bar will not move for the same amount of time, and that's
  even harder to detect a change in anyway. The average transfer speed
  also doesn't help; if you've had a long sustained transfer at 220k/sec
  (12 hours, say, so far) and the current speed is actually 6k/sec, the
  average won't change fast enough to be detected.

  Note: this is not a call for some sort of "fake progress indicator",
  like a spinner, unless that spinner actually stops spinning if
  progress stops. I had to resort to dropping to the terminal and "ls
  -lR"ing the copying files to see if the size of one of them was
  incrementing (which is very hard, because you don't know which one is
  currently being copied and it may be in a heavily nested subfolder).

  One obvious but user-hostile fix would be to show an actual byte count
  for amount copied (18253611008 bytes of 30GB copied) because you can
  see that changing. Another might be to change the "average speed
  counter" to much much more heavily weight recent changes to the speed,
  but it wouldn't be visible that that was actually the case and so
  would only help people who knew that nautilus did this. A third way
  might be to have a "details" expander which shows the name and byte
  count of the current file being copied (at which point this becomes
  fix 1, show the byte count, but hidden behind an expander).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/799601/+subscriptions