¡Hola Ben! El 2017-04-19 a las 17:27 -0700, Ben Longbons escribió:
Package: okular Version: 4:16.08.2-1+b1 Severity: normal
The following perfectly-legitimate, common, use of symlinks works with *all* programs that don't go out of their way to *break* it.
Okular manages to do this wrong, presumably by trying to do filesystem operations without, you know, talking to the filesystem.
#!/bin/sh set -e mkdir -p /tmp/okular-bug/ cd /tmp/okular-bug/ mkdir -p bar/baz echo 'Hello, World!' > bar/hello.txt ln -sf bar/baz foo cat bar/hello.txt okular bar/hello.txt cat foo/../hello.txt okular foo/../hello.txt
What do you mean with often fails? Is the "issue" not always reproducible with the shown command sequence?
Anyway, afaik, the behaviour using a path with a symlink to a dir and a ".." after it is not specified (please correct me if I'm wrong). The current behaviour is the expected one from a hierarchical filesystem point of view (creating a file in /tmp/okular-bug/hello.txt should open it).
My recommendation is to avoid using a mix of symlinks and .. in the path.I might tag the issue as wontfix in the future, but since I'm not sure if POSIX mandates a particular behaviour when following the parent dir of a symlink (nor I have found much about this) I haven't done so .
Also you might prefer to forward this report upstream reporting it in https://bugs.kde.org, if you do so, please add the reported issue url to this bug report.
Happy hacking, -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." -- Rich Cook Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: PGP signature