MuPDF v0.9-2 gives a segfault on Raspberry Pi running Raspian

Bug #1105308 reported by Alan Griffiths
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
Expired
Undecided
Unassigned

Bug Description

I reported this bug to the MuPDF team first (on bugzilla) and got the follwoing responses. They say it's a build problem in Raspbian... I've tried an "apt-get install mupdf" but it says my version is up-to-date.

--- Comment #2 from Robin Watts <email address hidden> ---
(In reply to comment #0)
> pi@raspberrypi ~ $ apt-cache showpkg mupdf
> Package: mupdf
> Versions:
> 0.9-2
> (/var/lib/apt/lists/mirrordirector.raspbian.
> org_raspbian_dists_wheezy_main_binary-armhf_Packages) (/var/lib/dpkg/status)
> Description Language:
> File:
> /var/lib/apt/lists/mirrordirector.raspbian.
> org_raspbian_dists_wheezy_main_binary-armhf_Packages
> MD5: 76c7b56de572593eec7cf1dec638601e
>
>
> Reverse Depends:
> Dependencies:
> 0.9-2 - libc6 (2 2.13-28) libfreetype6 (2 2.3.9) libjbig2dec0 (0 (null))
> libjpeg8 (2 8c) libopenjpeg2 (0 (null)) libx11-6 (0 (null)) libxext6 (0
> (null)) zlib1g (2 1:1.2.0) mupdf-tools (0 (null))
> Provides:
> 0.9-2 -
> Reverse Provides:

Actually, that looks like someone has packaged mupdf for Raspbian, but has done
so badly. This should be reported to the maintainers for Raspbian.

--- Comment #1 from Robin Watts <email address hidden> ---

http://bugs.ghostscript.com/show_bug.cgi?id=693585

Robin Watts <email address hidden> changed:

           What |Removed |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED |RESOLVED
                 CC| |<email address hidden>
         Resolution|--- |INVALID

--- Comment #1 from Robin Watts <email address hidden> ---
The clue to this is in the error message:

(In reply to comment #0)
> pi@raspberrypi ~ $ mupdf /usr/local/bin/indiecity/InstalledApps/the-magpi-issue-1/Full/The_MagPi_issue_1.pdf
> + fitz/filt_dctd.c:89: read_dctd(): jpeg error: JPEG parameter struct
> mismatch: library thinks size is 488, caller expects 448

You've got a build mismatch here. You are building with jpeg header files that
don't match the jpeg library you have installed. This is a problem with your
set up, and nothing to do with MuPDF itself. Sorry.

We recommend that you build either from:

 * the last released version of the source (using the libraries in the
mupdf-thirdparty.zip file available for download at the same location).

or

 * from sources obtained from git (using the thirdparty libraries available via
"git submodule update --init")

-----------------------------------------------------------------------------------------
MuPDF v0.9-2 gives a segfault on Raspberry Pi running Raspian:

pi@raspberrypi ~ $ mupdf /usr/local/bin/indiecity/InstalledApps/the-magpi-issue-1/Full/The_MagPi_issue_1.pdf
+ fitz/filt_dctd.c:89: read_dctd(): jpeg error: JPEG parameter struct mismatch: library thinks size is 488, caller expects 448
| fitz/stm_read.c:53: fz_read(): read error
Segmentation fault

pi@raspberrypi ~ $ apt-cache showpkg mupdf
Package: mupdf
Versions:
0.9-2 (/var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages
                  MD5: 76c7b56de572593eec7cf1dec638601e

Reverse Depends:
Dependencies:
0.9-2 - libc6 (2 2.13-28) libfreetype6 (2 2.3.9) libjbig2dec0 (0 (null)) libjpeg8 (2 8c) libopenjpeg2 (0 (null)) libx11-6 (0 (null)) libxext6 (0 (null)) zlib1g (2 1:1.2.0) mupdf-tools (0 (null))
Provides:
0.9-2 -
Reverse Provides:

Revision history for this message
Diederik (didi-debian) wrote :

Is this still an issue?
I tried to reproduce it on my jessie system, but it just worked just fine for me.

I have no idea why 'apt-cache showpkg mupdf' shows those 'null' values, but it does it here too.

Changed in raspbian:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Raspbian because there has been no activity for 60 days.]

Changed in raspbian:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.