After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660807 - File selection by typing is buggy sometimes
File selection by typing is buggy sometimes
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.2.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 643114 662065 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-03 17:51 UTC by Pedro Villavicencio
Modified: 2011-10-26 18:52 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-10-03 17:51:56 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/857710

"When I type in Nautilus to select files by name, often the wrong file is selected, as if my typing had been cut short or re-evaluated partway through. A screencast is attached."

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/857710/+attachment/2449405/+files/screencast.ogv
Comment 1 Sebastien Bacher 2011-10-11 09:17:12 UTC
there is a bug similar on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/872090

"On a Oneiric, open nautilus.
Click in the file and folder area.
Press backspace until you are in the root of the file system.
Type 'et'. Notice that the search box disappears after typing the second letter (Not expected, a bug).
Press enter to open the currently selected /etc.
Type 'ud' and notice that no search comes up (this is a bug).
Close nautilus and reopen.
Type 'docu' to select documents, press backspace to delete 'u' and press enter. Notice the search works as expected.
Press backspace to navigate up (this is working normal)
Type 'Public'. Notice search still works as expected. Press enter.
Press backspace until you are in the root of the filesystem."
Comment 2 Sebastien Bacher 2011-10-11 09:36:08 UTC
I can confirm that typeahead works weirdly in 3.2, the text entry often closes itself and then refuses to come back until you refresh the view
Comment 3 Erik Andersen 2011-10-11 16:44:31 UTC
The 'sometimes' part of this bug seems to be whether you are in your home folder or not. If you are in your home folder, everything works correctly (at least for me). If you are not in your home folder, it has the described problems. This is true even for the root user.
Comment 4 Sebastien Bacher 2011-10-12 09:30:53 UTC
it's not really specific to the user dir or not, browsing to another directory and going back to the user directory it seems to happen there as well, it might be "initially open directory against browsed ones"
Comment 5 bhaismachine 2011-10-13 22:34:19 UTC
I posted a similar bug today : https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/873678

I can confirm the above bug to be consistent with other users too.
Comment 6 Cosimo Cecchi 2011-10-17 20:28:45 UTC
I pushed a workaround for this in Nautilus, but I think this is actually a GTK bug, as I can reproduce the same issue with a reduced testcase: see https://bugzilla.gnome.org/show_bug.cgi?id=662036

Closing this bug anyway; the fix will be in Nautilus 3.2.1.
Comment 7 Sebastien Bacher 2011-10-17 20:33:54 UTC
Thanks a lot Cosimo!
Comment 8 Cosimo Cecchi 2011-10-18 12:53:47 UTC
*** Bug 662065 has been marked as a duplicate of this bug. ***
Comment 9 Cosimo Cecchi 2011-10-19 13:57:44 UTC
*** Bug 643114 has been marked as a duplicate of this bug. ***
Comment 10 Alexandre Provencio 2011-10-26 18:52:13 UTC
Unfortunately this bug is not solved for me yet on 3.2.1 (ubuntu release). While using type-ahead find, depending on which folder I am, I have two problems:
    - characters inside the type-ahead box don't get cleared when entering a dir, they accumulate. Even typing ESC won't do.
    - backspace press is not captured by the type-ahead box but from nautilus, causing backwards movement on the dir tree.

Should I open a new bug?