Package: mupdf
Version: 1.5-1+b2
Severity: normal

Dear Maintainer,

Since upgrading from Wheezy to Jessie upon the release of the latter, I can no
longer use mupdf to view PDFs I’ve encrypted with qpdf; those encrypted with
pdftk can be displayed.

I suspect that the problem is with mupdf rather than qpdf, because acroread
displays the files without demanding a password, and because acroread reports
that the files encrypted with qpdf can be opened with Acrobat 6.0 and later,
whereas those encrypted with pdftk require only Acrobat 5.0 or later.

If I type “mupdf filename.pdf” in an xterm, the output looks like this:

error: zlib error: incorrect header check
warning: read error; treating as end of file
error: corrupt object stream (3 0 R)
error: cannot open object stream (3 0 R)
error: cannot load object stream containing object (68 0 R)
warning: cannot load object (68 0 R) into cache
mupdf: warning: Invalid password.
error: Needs a password
mupdf: error: cannot open document

Thank you for packaging this very useful program!  And please excuse any
duplicate messages: google’s security measures were confused by reportbug and
blocked my first two attempts to report this.

Thérèse Bonin



-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mupdf depends on:
ii  libc6            2.19-18
ii  libfreetype6     2.5.2-3
ii  libjbig2dec0     0.11+20120125-1
ii  libjpeg62-turbo  1:1.3.1-12
ii  libopenjp2-7     2.1.0-2
ii  libx11-6         2:1.6.2-3
ii  libxext6         2:1.3.3-1
ii  zlib1g           1:1.2.8.dfsg-2+b1

mupdf recommends no packages.

Versions of packages mupdf suggests:
ii  mupdf-tools  1.5-1+b2

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to