From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] libjbig2dec: breaks mupdf with message "undefined symbol: jbig2_ctx_new"
Date: Fri, 04 Oct 2019 08:04:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15053@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
New issue by hereforthebugs on void-packages repository
https://github.com/void-linux/void-packages/issues/15053
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
* Void 5.2.18_1 x86_64 GenuineIntel uptodate rFFFF
* package:
* libjbig2dec 0.17
* mupdf 1.16.1_1
### Issue
After upgrading from libjbig2dec 0.16_1 to libjbig2dec 0.17, mupdf crashes with the message: 'mupdf: symbol lookup error: mupdf: undefined symbol: jbig2_ctx_new'
next reply other threads:[~2019-10-04 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 6:04 voidlinux-github [this message]
2019-10-04 6:58 ` voidlinux-github
2019-10-04 6:58 ` [ISSUE] [CLOSED] " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15053@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).