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 720463 - Nautilus pre-resolves symlinks before opening them
Nautilus pre-resolves symlinks before opening them
Status: RESOLVED DUPLICATE of bug 702301
Product: nautilus
Classification: Core
Component: general
3.8.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-12-14 16:32 UTC by Louis Jean-Richard
Modified: 2018-03-13 21:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Louis Jean-Richard 2013-12-14 16:32:23 UTC 
Instead of following the sequence of images in the browsed directory, eog upon hitting on a link immediately changes the browsed directory to the one containing the linked image.
Comment 1 Felix Riemann 2013-12-16 20:37:22 UTC 
This appears to be a Nautilus issue.
If you check how Nautilus launches eog (e.g. in gnome-system-monitor) you can see that Nautilus doesn't pass the symlink to eog but rather the linked file and as thus eog indexes the linked folder.
Comment 2 Matej 2013-12-19 15:51:18 UTC 
This is a serious issue. The bug prevents applications to work correctly with symlinks. 

In case of eog:
- eog displays target filename instead of symlink filename
- directory browsing in eog works not as expected; eog browses the target directory files instead of the symlink directory files
Comment 3 Tim Cuthbertson 2014-09-06 07:00:28 UTC 
I just hit this, and it nearly caused data loss due to the surprising behaviour. I thought I was deleting unwanted links to photos (cutting down the number of photos I wanted to publish), but eog was actually operating on the original folder because of this bug. Thankfully I realised before emptying the trash.
Comment 4 António Fernandes 2018-03-13 21:45:32 UTC 

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