Red Hat Bugzilla – Bug 247962
Evince can't open file through symlink on NFS
Last modified: 2008-05-15 09:44:13 EDT
Description of problem:
My home directory is mounted over NFS.
I have a PDF in ~/docs/Linux which I symlinked into ~/Desktop. If I click on the
PDF on my Desktop, evince starts but then gives an error dialogue.
Unable to open document
Unhandled MIME type: "application/octet-stream"
Running evince from the cli on the symlinked pdf produces the same problem.
Right clicking on the PDF then selecting to open in Xpdf works fine.
If I put the pdf into /tmp and then create a symlink also in /tmp then evince
works. If I symlink from /tmp to the file in my NFS'd home directory, evince works.
It seems to be only that if both the PDF and the symlink to it are on NFS then
evince doesn't work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a symlink to a pdf, where both are in a NFS mounted filesystem.
2. Try to open the pdf via the symlink with evince
Evince containing PDF.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Problem still persists in Fedora 8, will retest in Fedora 9 in a few days.
Works in Fedora 9