When moving, renaming, deleting files, their backup copies are not modified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Won't Fix
|
Wishlist
|
|||
nautilus (Ubuntu) |
Triaged
|
Wishlist
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: nautilus
When moving, renaming, and deleting files that have backup copies (those have the same filename with a tilde in the end, like 'filename~'), the backup copy is not affected by any such change to the main file. Since the backup copies are usually invisible (they are hidden by default), that leads to counter-intuitive experience, where as many files are moved, renamed, and deleted, they leave hidden traces that contain old information (which is potentially sensitive) and occupy disk space. Those remaining backup files usually have to be cleaned up manually, and some end up hanging around for a long time without being cleaned up.
One way to fix this is to automatically apply the same change (renaming, moving, or deletion) to the backup copy if one exist.
ProblemType: Bug
Architecture: i386
Date: Thu Aug 16 02:30:33 2007
DistroRelease: Ubuntu 7.04
Package: nautilus 1:2.18.1-0ubuntu1
PackageArchitec
SourcePackage: nautilus
Uname: Linux chronos 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
Changed in nautilus: | |
status: | Unknown → Confirmed |
Changed in nautilus: | |
status: | Incomplete → Triaged |
Changed in nautilus: | |
status: | New → Triaged |
Changed in nautilus: | |
importance: | Unknown → Wishlist |
Changed in nautilus: | |
status: | Confirmed → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. I don't get it why the backup copies should be renamed if you rename the original i mean thats why they are named "backups" and you should take care of them (deleting mostly). I have a couple of code backups files and i don't really want to deleted if for some mistake i delete the original one. Probably for renaming could work but not sure. Anyways feel free to open a report in the upstream bug database http:// bugzilla. gnome.org; thanks.