Bug 1286318 - Undesired behaviour on file rename
Undesired behaviour on file rename
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-27 20:05 EST by Viktor Jancik
Modified: 2016-07-19 15:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 15:22:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
nautilus-screenshot (11.13 KB, image/png)
2015-11-27 20:05 EST, Viktor Jancik
no flags Details

  None (edit)
Description Viktor Jancik 2015-11-27 20:05:55 EST
Created attachment 1099804 [details]

Description of problem:
I tried to rename a file in a folder to a name for which another file already existed in that folder.

This is what nautilus responded with (see attached picture).

I believe this isn't correct or desired behaviour. I think Nautilus should ask me if I want to overwrite the existing file.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Try to rename a file to a name for which a file already exists in that folder

Actual results:
You get a message saying you should choose another name.

Expected results:
You get a prompt asking if you'd like to replace the file.

Additional info:
Comment 2 Fedora End Of Life 2016-07-19 15:22:58 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.