thank you for your bug report, opening a pdf not named .pdf works fine
there, could you add an example to the bug?
** Changed in: evince (Ubuntu)
Importance: Undecided = Low
** Changed in: evince (Ubuntu)
Status: New = Incomplete
--
evince unable to open PDF file without suffix
Odd- this happens for all files I've tried.
I've attached a tarball that contains:
- pdftest.odt
- the resulting pdftest.pdf (written by OOo 3.2)
- the file pdftest, linked to pdftest.pdf
- a screenshot of the icons and file properties. Note that the suffixless
version is recognized as type PDF
Fixed it.
The problem was indeed related apparmor. My home directory is not in
/home and I didn't tell apparmor that. While testing Lucid, my home
directory is in /local/home-10.04, and /home - /local/home-10.4.
/etc/passwd and HOME specify /home/reece as my home directory.
The fix was to add
** Package changed: evince (Ubuntu) = apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Incomplete = New
--
evince unable to open PDF file without suffix
https://bugs.launchpad.net/bugs/532956
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The suffix is not required for files in your $HOME directory. Outside of
the $HOME directory, security policy is in place to make sure that only
legitimate documents and images supported by evince can be accessed.
This prevents things such as reading files in /etc.
As you discovered, this is
** Attachment added: evince error.png
http://launchpadlibrarian.net/40281149/evince%20error.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40280745/Dependencies.txt
** Attachment added: KernLog.txt
http://launchpadlibrarian.net/40280746/KernLog.txt
**
P.S. The modified conf is from an experiment to test whether app armor
might be at fault. It's not -- the absence of a suffix is sufficient to
cause the error.
--
evince unable to open PDF file without suffix
https://bugs.launchpad.net/bugs/532956
You received this bug notification because you
