Hide Forgot
On F25 dragging and dropping files from the main view to the places in the sidebar sometimes results in copy operations, sometimes in move operations, even though the target is on the same partition. There doesn't seem to be any consistency in when something will get moved or copied. I discovered that I had three copies of a screenshot for another bug report in three different places and then I started paying attention to the little arrow or cross next to the pointer when I click and drag a file over the target. Currently, I have nautilus-3.22.1-1.fc25.x86_64 installed. This happens more often than not, but I haven't figured an exact sequence that will reliably trigger this behavior. Most of the times, it is the Desktop folder and the first of my bookmarks that get files copied instead of moved there, but it can happen with other folders as well, e.g. Pictures. So far, I haven't seen the opposite behavior, i.e. having files moved instead of copied to other filesystems. This is on Xorg. I have set up a computer for a friend which runs GNOME on F25 Wayland, but he's out of town, I can have him take a look when he returns if anyone thinks it's necessary. I can't test it myself because I'm using nVidia's proprietary driver.
I've just heard back from my friend and he can't reproduce this behavior on Wayland.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.