This bug was fixed in the package evince - 2.32.0-0ubuntu2
---
evince (2.32.0-0ubuntu2) natty; urgency=low
* debian/control:
- Use standards-version 3.9.1
* debian/patches/02_libice.patch:
- Link against libice to fix FTBFS
[ Jamie Strandboge ]
*
Because there has been only one person reporting the issue, I 'd want to
confirm the issue. My version is Document Viewer 2.32.0 on Ubuntu 10.10. I did
not seem to have the issue on 8.04.
It also concerns a journal paper, that can be opened without problem after
renaming the extension.
--
** Changed in: evince (Ubuntu)
Status: Incomplete = In Progress
--
evince not allowed to open fdf files
https://bugs.launchpad.net/bugs/607573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: evince (Ubuntu)
Status: In Progress = Fix Committed
--
evince not allowed to open fdf files
https://bugs.launchpad.net/bugs/607573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: evince (Ubuntu)
Importance: Undecided = Low
--
evince not allowed to open fdf files
https://bugs.launchpad.net/bugs/607573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It is not clear to me that this is solely an AppArmor issue, since
evince is allowed to open files in $HOME. I tried an fdf file and evince
was unable to open it, but it was not blocked by AppArmor. Clearly, the
AppArmor profile does not support FDF files outside of $HOME. Can you
provide an
Sadly, I can't provide the exact file I was using, since it was a review
copy of a paper I'm refereeing for a journal. I can report that the
file utility reported the .fdf file was a regular PDF 1.4 file. I will
look for an example .fdf file that you can use.
--
evince not allowed to open fdf
