Created attachment 1273465 [details] Journald log captured while moving files Description of problem: If there are both files and folders inside current directory and you try to drag a file or folder from current directory to one of the sub-directories, it works for the first time immediately. However, on subsequent attempts, the file remains as as i.e. its not moved to the sub-directory for about 30-40 seconds and then suddenly it is moved. This happens with both very small and fairly big files. Version-Release number of selected component (if applicable): Nautilus ================ nautilus-3.24.0-1.fc26.x86_64 Plugins ============== rabbitvcs-nautilus-0.16.1-0.7.20160108gite8214e6.fc26.noarch totem-nautilus-3.24.0-1.fc26.x86_64 nautilus-sendto-3.8.4-2.fc26.x86_64 nautilus-python-1.1-12.fc26.x86_64 evince-nautilus-3.24.0-1.fc26.x86_64 gnome-terminal-nautilus-3.24.1-1.fc26.x86_64 brasero-nautilus-3.12.1-5.fc26.x86_64 nautilus-extensions-3.24.0-1.fc26.x86_64 How reproducible: In a folder with files and subfolders, try to drag and drop a file to a subfolder. It will be moved immediately. Try the same thing again with another file to same or different subfolder. It will happen after 30-40 seconds. Steps to Reproduce: 1. Open a folder with both sub folders and files. 2. Drag and drop a file to one of the subfolders. It will move inside it immediately. 3. Again try to drag and drop a file to any of the subfolders, this time onwards the file will not be moved to the subfolder immediately. It will happen after 30-40 seconds. Actual results: File is moved to subfolder on first and subsequent attempts immediately. Expected results: File is moved on first attempt immediately but not on subsequent attempts. Additional info:
This issue also happens on F24 and F25 by the way. See also this upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=775860
Discussed in 2017-05-08 Blocker Review Meeting. Before we can vote on this we need a proposed fix so we can see how tricky it is. We'll revisit next week.
Discussed at 2017-05-22 blocker review meeting: [1]. This bug was rejected as Freeze Exception: This bug lacks the information we need to determine how invasive it would be and no one in the meeting could reproduce it. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-05-22
Can you reproduce this bug with a newest version of nautilus. We (people on the blocker review meeting) were unable to reproduce this. Thanks
Ok, I retested it and I was able to reproduce. But after moving the file second time, when it didn't move, I waiting for some time and then got an error message dialog that says: "There was an error getting information about rabbitvcs-about." Under Show More Details dropdown, it says: "Operation not supported." So I guess the issue is not with Nautilus but with RabbitVCS that i have installed for SVN access. I think this bug can be closed, I will raise another with RabbitVCS team.