Comment 11 for bug 1184720

Revision history for this message
Paál, Balázs (paalb) wrote :

Trusty is still affected. This is a *very* annoying bug, could it be fixed in 14.04, please?
If the fix is not available soon, some users (including myself) may be forced to install another file manager. (c.f. discussion of gnome bug https://bugzilla.gnome.org/show_bug.cgi?id=702301)

N.B. some people beleive this is a medium or low priority issue. However, in setups like the ones mentioned on gnome bugzilla, this bug makes nautilus essentially unusable for many tasks. And it's not merely about "navigating back" or "navigating up". The real problem comes when you open a file *after* navigating the symlink. The application that is lauched will get the dereferenced path, and may calculate its own references from there.

I frequenly use LibreOffice documents with several embedded linked files. If the document is fired from the wrong (i.e. dereferenced) location, then all internal references will be screwed, or at least the document will contain different references (some with the unreferenced symlink path, some with the dereferenced path). This is very annoying when you want to move your document to another location, hunting down broken links is a nightmare.

The same goes for any application like video or music editing, where a project file contains links to resource or material files. You will have total confusion, two different types of references will be stored in your project. Some applications then behave differently with the references that are "along the project path" from those that seemingly are "external to the project path".

Please DO revert this to the earlier, (expected linux standard) symlink behavior in 14.04, as soon as possible.