Created attachment 843244 [details] How it looks like when the bug is triggered Description of problem: Nautilus freezes when you start to search for a file on a network share. It usually happens after you type the first three letters into the nautilus search bar and try to open the search result. The gvfsd-sftp process starts consuming 100% CPU and the Nautilus GUI freezes. Version-Release number of selected component (if applicable): nautilus.x86_64 3.10.1-2.fc20 gvfs.x86_64 1.18.3-2.fc20 How reproducible: Type in nautilus on a network share the first 3 letters of a file/folder you whant to search for. Steps to Reproduce: 1. Open nautilus 2. Connect to a network share over sftp 3. Open a network share folder containing some files 4. Start typing the first 3 letters of the folder you want to search for 5. Double-click on the folder you searched in the search result window Actual results: Nautilus freezes and does not recover. The process gvfsd-sftp consumes 100% CPU. After killing the nautilus process, the network share cant't be accessed anymore. Unmounting of the network share is also not possible. Expected results: Double-click on a search result folder should open the folder in nautilus and show the content. Additional info: As I can't always reproduce it on first run, you will have to repeat step 4. and 5. with different search queries several (usually less than 10) times.
This bug also happens for me using Ubuntu 13.10. So this is probably an upstream bug, not Red Hat-specific.
Hi, this bug affect also my PC (Latitude E5540) Fedora release 20, Name : nautilus Arch : x86_64 Version : 3.10.1 Rilease : 4.fc20 Name : gvfs Arch : x86_64 Version : 1.18.3 Release : 2.fc20
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.