You are not logged in.
Hi,
I recently (on 2013-03-18) updated community/zathura-pdf-mupdf (0.2.2-1 -> 0.2.3-1), and since I did that, I can't see some images in PDF's. The terminal from which I called zathura outputs:
error: jpeg error: Wrong JPEG library version: library is 80, caller expects 90
warning: Ignoring error during interpretation
suggesting that I have an older jpeg library than it wants. I checked /usr/lib, and in it I have "libjpeg.so.8.0.2". Also, I have mupdf 1.2-1, zathura 0.2.2-1, libjpeg-turbo 1.2.1-1, and have run a "pacman -Syu" within the last hour.
I'm guessing zathura wants a newer version of libjpeg-turbo than is in the repositories, but I'm not sure. Thoughts?
Thanks.
Offline
Same here, my pdf's aren't rendering correctly either. I'm switching over to llpp for now then.
Last edited by johan1391 (2013-03-20 22:54:56)
Offline
Apparently it is requiring the beta for libjpeg-turbo: http://sourceforge.net/projects/libjpeg-turbo/files/
The repository has the latest stable version. Actually, this looks like a good candidate for someone to roll together for the AUR. I would look at perhaps modifying this PKGBUILD for your purposes.
Last edited by the sad clown (2013-03-21 00:16:38)
I laugh, yet the joke is on me
Offline
Thanks for the feedback. I'm not sure about the libjpeg-turo beta suggestion though, because on the sourceforge page (http://sourceforge.net/projects/libjpeg-turbo/), it says that it only can do v6b, v7, or v8. In addition, from the main libjpeg-turbo page, they suggest at http://www.libjpeg-turbo.org/About/Jpeg-9 that they don't plan to support jpeg-9. Perhaps it might work with https://aur.archlinux.org/packages/libjpeg9/ from the AUR, though I haven't tried it.
Offline
My link showed that there is a libjpeg-turbo 1.2.90 (1.3beta1). I don't know what you read, but it's there.
I laugh, yet the joke is on me
Offline
@the sad clown, muon is right libjpeg-turbo don't support JPEG version 90 in any current stable or beta and they don't plan to add support to it. Read the links muon posted.
I found the problem and reported here https://bugs.archlinux.org/task/34590 a workaround is included in the bugreport.
Last edited by kazuo (2013-04-03 20:23:09)
Offline