[Expired for evince (Ubuntu) because there has been no activity for 60
days.]
** Changed in: evince (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1835285
Title:
PDF files don't open; "Failed to load backend for 'application/pdf':
libpdfdocument.so" and "Invalid ELF header".
Status in evince package in Ubuntu:
Expired
Bug description:
Hello.
On Wed, Jun 19. 2019, Evince has been updated to version
'3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
hardening from Ubuntu 18.10 Release. However, now, it is impossible to
open any '.pdf' files. When I try to open such file, there is an
information (on the red background) in the main Evince window. And It
looks this way:
,----[ Opening '.pdf' error ]
|
| Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
| Failed to load backend for 'application/pdf':
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF
| header
|
`----
There is a reference to »/usr/lib/i386-linux-
gnu/evince/4/backends/libpdfdocument.so«. According to `dpkg(1)`
command this file is a part of the 'libevdocument3-4' package, which
is installed already (version '3.18.2-1ubuntu4.5'). I also tried to
open '.pdf' file via terminal, but nothing changed. Here are the
results:
,----[ $ evince Docs/foo-bar.pdf ]
|
| (evince:26918): EvinceDocument-WARNING **:
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF
| header
|
| (evince:26918): EvinceDocument-WARNING **:
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF
| header
|
`----
I think, that the whole problem is/could be related with AppArmor and
Evince profile changes in the latest update, because - for example -
day before, before update, everything was okay. Anyway, described
problem/issue started to happen right after Evince update. (To check
differences between AppArmor profile versions, please see 2. and 3.).
There is one more thing to notice: Evince profile, has never been
changed by the User.
If it's about AppArmor: I've tried to change Evince profile mode from
'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't
any valuable entries in system log files etc. (I'm sorry, but for now,
I can not check other variants/solutions, such as: (a) disable Evince
profile via `aa-disable(8)` command or (b) make links between
»/etc/apparmor.d/usr.bin.evince« file and »/etc/apparmor.d/disable/«
directory, next use `apparmor_parser(8)` command to remove profile
etc.)
✖ NOTE: to make some more tests, I've tried to open '.djvu' file, but
without success. It seems, that there is exactly the same informations
as with '.pdf' files. Of course, Evince
(»/etc/apparmor.d/usr.bin.evince«) profile contains rule to open such
file format etc. and many others, see 4. So, according to all of this,
maybe "Summary" should be changed to reflect this situation? Maybe
something like: "PDF and other files don't open; "Failed to load
(...)".
Sebastien, what do You think?.
Here are some additional informations:
✗ Description: Ubuntu 16.04.6 LTS
✗ Release: 16.04
✗ Architecture: x86_32/i386
✗ Linux: 4.4.0-155-generic
✓ AppArmor: 2.10.95-0ubuntu2.11
✓ Evince: 3.18.2-1ubuntu4.5
Best regards.
______________
[1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html
[2]
http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz
[3]
http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz
[4]
https://wiki.gnome.org/action/show/Apps/Evince/SupportedDocumentFormats?action=show&redirect=Evince%2FSupportedDocumentFormats
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
