Bug#850163: xpdf/poppler miscommunication

[Albert Astals Cid <aacid@kde.org>]

El diumenge, 19 de febrer de 2017, a les 23:00:53 CET, Andries E. Brouwer va 
escriure:
> If you prefer to give that program a different name, let us call it xyzpdf.
> So, the situation is that there is a widely used program called xyzpdf.
> This program uses libpoppler, that is, ldd shows
> 
> % ldd /usr/bin/xyzpdf
> ..
> libpoppler.so.58 => /usr/lib/x86_64-linux-gnu/libpoppler.so.58
> 
> Now this libpoppler as used by this program fails to work.
> Maybe libpoppler is not buggy, but it blindly uses invalid data.

You want libpoppler to be Clippy?

Sincerely, if you tell poppler the data is in /foo it'll read /foo, if the 
data is not htere, though luck, maybe you want to fix the widely used program 
called xyzpdf to not tell poppler that the data is in a location /foo that 
doesn't really hold the data

Best Regards,
  Albert