Bug 1302067 - Nautilus: MOVE TO directory chooser used wrong directory
Nautilus: MOVE TO directory chooser used wrong directory
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-26 12:18 EST by christa@arwoschwarz.de
Modified: 2016-12-20 13:14 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 13:14:06 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot of the problemativ directorychooser (212.04 KB, image/png)
2016-01-26 12:20 EST, christa@arwoschwarz.de
no flags Details

  None (edit)
Description christa@arwoschwarz.de 2016-01-26 12:18:28 EST
Description of problem:

We have as path : christa/Bilder/FotosPC

We want to move pictures out of FotosPC into Bilder. 

We used right-click context menu on a picture,
pressed on Bilder Button in the upper PATHrow above the directory content
and with "auswählen" => "select/choose" we ended up with the selected 
path we came from "christa/Bilder/FotosPC" instead of "christa/Bilder"

Same procedure, but instead of the Bilder in the upper pathrow, we used the shortcut on the sidebar to select the directory, we got the correct result.

This is wrong: 

The problem comes from the auto selection of the subdirectory we came from,
where as with the sidebar button way, we do not end up with the selected subdirectory in the first place. 

suggested solution: 

do not autoselect the subdirectory, if the upper buttons are used to selected an upwards directory as target.

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


How reproducible:


Steps to Reproduce:

see above 

Actual results:

Wrong directory

Expected results:

selected directory.

Additional info:

This bug has been created by a none english speaker, so pls give easy answeres or revert to german if possible. Thank you.
Comment 1 christa@arwoschwarz.de 2016-01-26 12:20 EST
Created attachment 1118555 [details]
screenshot of the problemativ directorychooser
Comment 2 Fedora End Of Life 2016-11-24 10:13:12 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2016-12-20 13:14:06 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.