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 656084 - Nautilus two pane view, unfocused pane can't be accessed by mouse click
Nautilus two pane view, unfocused pane can't be accessed by mouse click
Status: RESOLVED DUPLICATE of bug 662893
Product: nautilus
Classification: Core
Component: Location Bar
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-06 20:00 UTC by sam_
Modified: 2012-02-14 02:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sam_ 2011-08-06 20:00:53 UTC 
Nautilus with enabled location bar (Ctrl+L), two pane view (F3) and side pane with tree view.
The unfocused location bar doesn't allow to be clicked on in order to change focus of panes or to edit for example the path.
Access is possible in Nautilus 2.23.2.1 (Ubuntu Natty).
If the two panes are full with folders and files, there is no empty area to click on.
The remaining choices to switch between the two panes are then only shortcuts or location bar.
Expected.
Allow unfocused location bar to be accessible again with mouse click.

First reported there.
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/822063
Comment 1 sam_ 2011-12-19 17:52:27 UTC 
Still the case in version 3.2.1
nautilus:
  Installed: 1:3.2.1-2ubuntu4
  Candidate: 1:3.2.1-2ubuntu4
  Version table:
 *** 1:3.2.1-2ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
Comment 2 Cosimo Cecchi 2012-02-14 02:35:39 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 662893 ***