Seems to be an intentional security feature. File extensions are
restricted by the files /etc/apparmor.d/usr.bin.evince and
/etc/apparmor.d/abstractions/evince.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Still present in 3.6.1-1ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/444907
Title:
PDF files with wrong extension fail to load
To manage notifications about this bug go
This also occurs with TIFF files or presumably any other file format.
Evince seems to be processing files based on file extension rather than
magic. I was just very confused by processing files with gm convert
+adjoin $i.pdf $i.tiff (from within a for loop) and being unable to
open the resulting
Updated the title as it seems that no matter what I rename the extension
of a PDF file as (as long as it's not .pdf), Evince will refuse to
load it.
** Summary changed:
- Files with extension .ashx fail to load
+ PDF files with wrong extension fail to load
--
You received this bug notification
