Same here, it seems to be a problem on gnome_vfs_async_xfer callback that returns wrong values for sizes:
(gdb) p *info
$6 = {status = GNOME_VFS_XFER_PROGRESS_STATUS_OK, vfs_status = GNOME_VFS_OK,
  phase = GNOME_VFS_XFER_PHASE_COPYING,
  source_name = 0x8e98f78 "http://bugzilla.gnome.org/bugzilla.gnome.org/bugzilla-config.xml",
  target_name = 0x8e90750 "file:///home/fer/.gnome2/bug-buddy.d/bugzilla/gnome/config.tmp",
  file_index = 2, files_total = 6, bytes_total = 6144, file_size = 0, bytes_copied = 0,
  total_bytes_copied = 6946, duplicate_name = 0x8e81a58 "config.tmp", duplicate_count = 0,
  top_level_item = 1, reserved1 = 0xb7c4a218, reserved2 = 0x3c71a8}

where total_bytes_copied should not be greater than bytes_total. It seems that bytes_total shows only the size for the first file.

have you filed a gnome-vfs report about this?

a temporary hack would simply set fraction=1 if fraction>1

Ok, I filled the gnome-vfs bug and making this depend on that. I dislike the temp hack because I don't like to obscure real bugs. Let me try to fix it :)

I don't like temp hacks either, but in this case I'd do it because we need a working bug-buddy :)
I am thinking about a compiler #warning in the code so that the temp hack will not be forgotten.

Created attachment 56819 [details] [review]
compute fraction and set it to 1 if greter than 1

fixes critical warning.
should be removed if the gnome-vfs issue has been resolved.

*** Bug 325069 has been marked as a duplicate of this bug. ***

*** Bug 326068 has been marked as a duplicate of this bug. ***

The gnome-vfs bug has been fixed on which this bug depends on.

Fer, I suggest you make a release (you wanted anyways if I remember correctly)
and then undo the patch and close this report.

*** Bug 327018 has been marked as a duplicate of this bug. ***

fer, I believe the temporary patch can be backed out.

I just tested - can be removed savely now.

the code is gone in latest bug-buddy and the gnome-vfs issue has been solved.