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 139384 - nautilus network access documentation is out of date
nautilus network access documentation is out of date
Status: RESOLVED DUPLICATE of bug 324966
Product: nautilus
Classification: Core
Component: Documentation
2.8.x
Other All
: Normal major
: ---
Assigned To: John Fleck
Nautilus Maintainers
: 143132 145119 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-07 15:53 UTC by Arcterex
Modified: 2006-01-17 22:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Arcterex 2004-04-07 15:53:12 UTC 
According to a reply from gnome-desktop-devel, section 7.8.2 of the nautilus documentation describes 
how version 2.4 worked, not 2.6.  In particular the sections about the NFS object and the 'Add Network 
Place' object simply don't exist in the newest nautilus, and this causes user confusion and frustration 
when trying to learn about the new file manager.
Comment 1 Tim Herold 2004-06-11 12:58:17 UTC 
*** Bug 143132 has been marked as a duplicate of this bug. ***
Comment 2 John Fleck 2004-06-11 14:10:22 UTC 
Thanks. We've got a rewrite of the docs underway. We'll add this....
Comment 3 Christian Neumair 2004-10-20 16:36:27 UTC 
Nautilus 2.8 seems to be a lot better in this respect. Is it still an issue?
Comment 4 Matthew Gatto 2004-11-06 06:08:18 UTC 
It still seems to be out of date on 2.8.

In Section 7.8.2.1, it talks about [ Places -> Computer -> 'Add Network Place'
object ] which doesn't seem to exist anymore. Section 7.8.3 doesn't seem to be
applicable anymore either.
Comment 5 Christian Neumair 2005-07-20 18:27:31 UTC 
*** Bug 145119 has been marked as a duplicate of this bug. ***
Comment 6 Joachim Noreiko 2006-01-17 22:36:00 UTC 
marking as a duplicate of a newer bug with documentation fixes for this.

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