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 159661 - Symlinks in the root directory are incorrectly resolved
Symlinks in the root directory are incorrectly resolved
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2004-11-27 21:45 UTC by Daniel Thompson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A very-likely-broken patch that works for me. (831 bytes, patch)
2004-11-27 21:49 UTC, Daniel Thompson
none Details | Review

Description Daniel Thompson 2004-11-27 21:45:47 UTC
Create a path from / with a relative symlink in it.

For example:
cd /
mkdir -p a/b/c
ln -s a/b .
cd a
ln -s b/c .

Now place any picutre in /a/b/c and navigate through it with gthumb. Although
/a/b/c and /a/c will display thumbnails correctly /b/c will not (the holding
images are never replaced).

This is a real problem for me since on my machine /home is a link to
usr/local/home meaning I unable to see any thumbnails in my home directory (and
for the same reason the comments for my images have been orphaned).
Comment 1 Daniel Thompson 2004-11-27 21:49:56 UTC
Created attachment 34198 [details] [review]
A very-likely-broken patch that works for me.

This problem is due to a bug in resolve_all_symlinks. The symlink resolver
converts /home into /home/usr/local/home rather than /usr/local/home. When the
error is noticed that path is converted back to /home and we try again
(eventually reaching the 32 symlink limit and giving up).

I have fixed this problem for my own machine by resolving against the symlinks
parent (/ in this case) rather than the link itself. This fixes the problem
without causing any regressions in the /a/b/c case above.
Comment 2 Paolo Bacchilega 2004-11-28 10:40:12 UTC
Fixed now, thank you.