FS#65880 - [mupdf] JBIG2-encoded pages fail to render

Attached to Project: Community Packages
Opened by Lewis Pike (ntwk) - Wednesday, 18 March 2020, 14:43 GMT
Last edited by Christian Hesse (eworm) - Monday, 30 March 2020, 18:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

The jbig2dec library was recently upgraded from 0.17 to 0.18. With jbig2dec 0.18 installed, mupdf 1.16.1-2 now fails to display JBIG2-encoded pages. The error reads:

warning: jbig2dec error: incompatible jbig2dec header (0.17) and library (0.18) versions (segment -1)
error: cannot allocate jbig2 context
warning: Ignoring error during interpretation
mupdf: warning: Errors found on page. Page rendering may be incomplete.

Current workarounds:

- Downgrading jbig2dec to 0.17 fixes the problem.
- Rebuilding mupdf 1.16.1 against jbig2dec 0.18 fixes the problem.

Additional info:
* package version(s):

- mupdf-1.16.1-2-x86_64
- jbig2dec-0.18-1-x86_64

Steps to reproduce:

1. Update the Arch Linux system via pacman -Syu.
2. Open a JBIG2-document in mupdf.
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 30 March 2020, 18:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  mupdf 1.16.1-3
Comment by Sachin Krishnan (sachkris) - Thursday, 19 March 2020, 12:33 GMT
The same upgrade also seems to break ghostscript.

GPL Ghostscript 9.51 (2020-03-12)
Copyright (C) 2020 Artifex Software, Inc. All rights reserved.
This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY:
see the file COPYING for details.
Processing pages 1 through 1.
Page 1
jbig2dec FATAL ERROR decoding image: incompatible jbig2dec header (0.17) and library (0.18) versions
Comment by sekret (sekret) - Saturday, 21 March 2020, 19:45 GMT
I just ran into a problem with mupdf, when I opened a pdf file created with a book scanner. It happens with all such files (I have plenty of them to try). I first opened it with evince. No problem here. Then I just recompiled mupdf in a clean chroot, installed it and well, everything's fine.

So this is an easy fix! Just bump the pkgver, rebuild it and push it to the repos, done.

edit: Sorry, the version I was writing about is 1.16.1-2
Comment by Daniel Lublin (quite) - Thursday, 26 March 2020, 19:22 GMT
I really think it just needs to be recompiled with 0.18 headers. I spoke to one of the devs of jbig2dec, and he said that we're at version 0.x and breaking changes can be expected.
Comment by Christian Hesse (eworm) - Thursday, 26 March 2020, 19:40 GMT
Please try mupdf 1.16.1-3.
Comment by Toni Jarjour (Tonij) - Thursday, 26 March 2020, 21:24 GMT
I'm using Zathura, which doesn't use the mupdf package at all. It has its own optional dependency: https://www.archlinux.org/packages/community/x86_64/zathura-pdf-mupdf
Comment by Lewis Pike (ntwk) - Monday, 30 March 2020, 16:56 GMT
This issue appears to be fixed in mupdf 1.16.1-3. I am requesting that this bug report be closed.

Loading...