Thunar doesn't manage well the interruption of copy process: If I start copying something using thunar and then I cancel the process, what has been copied for this time remains. This is useless, because an incomplete file is unusable, infact Windows Explorer, Finder and old versions of Thunar (as of June 2010: http://forum.ubuntu-it.org/index.php/topic,389663.msg3026519.html#msg3026519) erase the incomplete files. This behaviour is very unfriendly because if the user repeats again the operation later thunar could not disinguish between complete and incomplete files, forcing the user to repeat the whole operation overwriting all files or checking them one by one. The problem could also lead to data loss, if the user isn't aware of this behaviour, he may think that all the file listed in the target folder have been correctly copied and skip them when repeating the operation. OS: arch x86_64 xfce4 4.8.1-2 thunar 1.2.2-1 This is not really a bug rather a "feature bug" which has been added. Nautilus, dolphin and pcmanfm has always have suffered this, 2010-thunar no, why it has been added this "feature bug" in 2011? nautilus: https://bugzilla.gnome.org/process_bug.cgi nautilus again: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/810991
UP: the GNOME's link is wrong, here is the right one https://bugzilla.gnome.org/show_bug.cgi?id=654571
I can confirm this bug. Beginning a MOVE operation of a file of 700Mbfrom a Thunar window to another one, I decided quickly to cancel the move, because indeed the file's existing on the target folder, being identical to the source in size and time. After canceled the operation, the target file was reduced to 17Mb. SYSTEM INFORMATION Running Ubuntu Linux, the Ubuntu 11.10 (oneiric) release. GNOME: 2.32.1 (Ubuntu 2011-04-14) Kernel version: 3.0.0-26-generic-pae (#42-Ubuntu SMP Wed Sep 5 08:58:09 UTC 2012) GCC: 4.6.1 (i686-linux-gnu) Xorg: 1.10.4 (19 October 2011 05:09:41AM) (19 October 2011 05:09:41AM)
sorry, forgetting: Thunar version is 1.2.3
Resolving duplicate. *** This bug has been marked as a duplicate of bug 3004 ***