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 608525 - Using command options to open to a specific folder, Tree view side panel does not start at the correct folder
Using command options to open to a specific folder, Tree view side panel does...
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-30 14:18 UTC by Michael Lueck
Modified: 2012-09-05 12:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Lueck 2010-01-30 14:18:08 UTC 
I like to create multiple Nautilus Gnome launcher icons to be rooted at various spots on my file-system.

I use the following command line syntax to start Nautilus instances at a specific directory:

nautilus --no-desktop --browser %U /mnt/servername/shareonserver

The general pain does open to the correct location.

What is broken is that I have the Tree View selected for the left side bar. Using this syntax should pre-select the correct folder in the tree view. It does not.

Even if I click in the general/right side a sub-folder of the specified location, the tree view left side pane still does not catch up all of the way with the proper location in the tree view.

If I click the left-pain tree view and locate the correct place, THEN it finally starts tracking correctly between left/right panes.

I am re-verifying this morning with the latest Ubuntu Lucid alpha with all patches applied.

*** Aaahh... I just found something! ***

It actually CAN work as expected, IF I ONLY HAVE ONE Nautilus INSTANCE OPEN! With multiple Nautilus windows open, however, this behavior yet persists in 2.29.2 build. So, getting better, just not perfect yet.
Comment 1 William Jon McCann 2012-09-05 12:05:12 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.