After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 615254 - Dialog box open when overwriting/replacing files with the same name can cause data loss
Dialog box open when overwriting/replacing files with the same name can cause...
Status: RESOLVED DUPLICATE of bug 134251
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-09 07:27 UTC by alanmoore2000-foros
Modified: 2010-04-09 09:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description alanmoore2000-foros 2010-04-09 07:27:45 UTC
When the user is moving or copying a file to a directory which has a file with the exact same name, a dialog box appears asking the user if he/she wants to overwrite the existing file with the new one, or skip the operation. The problem I see, and it's a major one, is that the dialog box doesn't show any information about the files involved to help the user make a decision. It shows neither file size nor last modification date/hour. It's a very old bug with potential data loss for the user, who can overwrite a file which he/she doesn't really want to lose.

Dolphin is much better at that, as also is pcmanfm2. Heck, even Windows Explorer shows useful information to the user. Altough a traditional Gnome user, I'm changing myself to pcmanfm2 beta to avoid this issue.

Now that nautilus is reinventing itself for Gnome 3, what about fixing one of its oldest and most dangerous bugs?
Comment 1 Cosimo Cecchi 2010-04-09 09:52:21 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 134251 ***