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 652704 - nautilus-3.0.2 uses the first instance's directory for all relative directories provided as command line parameters in later instances
nautilus-3.0.2 uses the first instance's directory for all relative directori...
Status: RESOLVED DUPLICATE of bug 649336
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-16 09:27 UTC by Mike Auty
Modified: 2011-06-19 20:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mike Auty 2011-06-16 09:27:50 UTC
Hiya,

Just a quick report that the following does act as expected (or previous versions):


$ nautilus /some/first/directory & disown
$ cd /second/directory
$ nautilus .

Expected results
================

Two windows, one showing /some/first/directory, and the second showing /second/directory.

Actual results
==============

Two windows, both showing /some/first/directory.


As best as I can tell, whichever directory is specified on the command line when nautilus is first run (/home/user if not specified) will be used for all relative addresses for later instances.

In the following example:

/home/usera/stuff
/home/userb/things

$ cd /home/usera
$ nautilus & disown
$ cd /home/userb
$ nautilus ./things

This will raise an error that "/home/usera/things" does not exist.

If there's any further information or testing I can do, please let me know...
Comment 1 Mike Auty 2011-06-16 09:29:34 UTC
(Sorry for the bugspam!)  5:(
Comment 2 André Klapper 2011-06-19 20:53:27 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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