number of deleted files is bigger that total files to be deleted

Thank you for the bug report. Also, please answer these questions:

* Which are the steps that lead to it?

This will greatly aid us in tracking down your problem.

I open the trash icon for have a trash window in the nautilus. After I press to Empty trash on the up-right corner of the nautilus. Then all files is deleted (normal), but on dialog number of deleted files is bigger that all filles for delete.
May be only traduction slovque is wrong...
See screen-shot attached.

Si j'ouvre nautilus, et puis je si j'appuye sur Vider la corbielle, sur le diaglogue il y a plus des fichier en train d'effacer que le nombre compete des fichier.
Peut-etre seulement la traduction slovaque n'est pas correcte.
Voir le dialog ajouté.

Can you attach the following:

1. run "ls -aR ~/.Trash > ~/trash_files.txt" and attach trash_files.txt
2. run "mount -l > ~/mount.txt" and attach mount.txt

Also, is this bug a one time event or happens every time?

for #1, can you run "ls -alRh ~/.Trash > ~/trash_files.txt", I want to see the files permissions also.

Thanks

Bug is apears aĺways when I want to empty trash.

I attache a list of files. Some of files is not owner of marek (user own) in .Trash

Thanks

Ok, can you run the following command "ls -lhaR /data/.[tT]rash* /home/.[tT]rash* /windows/.[tT]rash* > trash_files_mount.txt"

and that should be good enough to debug...

The following commandes:
ls -lhaR /data/.[tT]rash* /home/.[tT]rash* /windows/.[tT]rash* >trash_files_mount.txt 2>&1
sudo ls -lhaR /data/.[tT]rash* /home/.[tT]rash* /windows/.[tT]rash* >trash_files_mount_sudo.txt 2>&1

are output in attachement.
I m ready to help you if need...

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=439258 . I've also added you to the CC's list for that bug.

could you try if that's still an issue in hardy? lot of code has been rewritten and it might have been fixed there

upstream closed the bug doing the same, feel free to reopen if you still get the issue though