[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#807788: texworks crashes looking for libpoppler.so.47



Package: texworks
Version: 0.5~svn1363-6+b1
Severity: normal

Dear Maintainer,

With the most recent updates to Poppler 0.38 the shared object library coded instead of linking to libpoppler.so is linked to libpoppler.so.47 TeXWorks crashes as the new version is libpoppler.so.57.

Workaround:

mdriftmeyer@horus:/usr/lib/x86_64-linux-gnu$ sudo ln -s libpoppler.so libpoppler.so.47

Then TeXWorks launches. I'd prefer TeXWorks link against the most current version of libpoppler.so so then it doesn't break when libpoppler.so update links to the next libpoppler.so.5x or libpoppler.so.6x

- Marc

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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 texworks depends on:
ii  libc6               2.21-4
ii  libgcc1             1:5.3.1-3
ii  libhunspell-1.3-0   1.3.3-3+b2
ii  libpoppler-qt4-4    0.38.0-2
ii  libpoppler57        0.38.0-2
ii  libqt4-dbus         4:4.8.7+dfsg-5
ii  libqt4-script       4:4.8.7+dfsg-5
ii  libqt4-scripttools  4:4.8.7+dfsg-5
ii  libqt4-xml          4:4.8.7+dfsg-5
ii  libqtcore4          4:4.8.7+dfsg-5
ii  libqtgui4           4:4.8.7+dfsg-5
ii  libstdc++6          5.3.1-3
ii  libsynctex1         2015.20150524.37493-7+b1
ii  zlib1g              1:1.2.8.dfsg-2+b1

Versions of packages texworks recommends:
ii  gsfonts             1:8.11+urwcyr1.0.7~pre44-4.2
ii  poppler-data        0.4.7-5
ii  texlive-latex-base  2015.20151116-1
ii  texworks-help-en    0.5~svn1363-6

Versions of packages texworks suggests:
ii  texlive-xetex              2015.20151116-1
ii  texworks-scripting-lua     0.5~svn1363-6+b1
ii  texworks-scripting-python  0.5~svn1363-6+b1

-- no debconf information


Reply to: