Bug#931010: xpdf: When xpdf fails on startup (e.g. due to unsupported PDF file), it does not show an error message
Package: xpdf
Version: 3.04-13
Severity: normal
When xpdf fails on startup (e.g. because the PDF file provided in
the command line is invalid or not supported), it does not show an
error message. Error on stderr is not sufficient because it may not
be visible.
Firefox is affected by this issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=1318331
(closed as WONTFIX, as it is regarded as a bug in xpdf), i.e. there
is no feedback, so that the user wonders what's going on.
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xpdf depends on:
ii libc6 2.28-10
ii libgcc1 1:8.3.0-7
ii libpaper1 1.1.27
ii libpoppler82 0.71.0-5
ii libstdc++6 8.3.0-7
ii libx11-6 2:1.6.7-1
ii libxm4 2.3.8-2
ii libxt6 1:1.1.5-1+b3
Versions of packages xpdf recommends:
ii cups-bsd 2.2.10-6
ii gsfonts-x11 0.26
ii poppler-data 0.4.9-2
ii poppler-utils 0.71.0-5
ii sensible-utils 0.0.12
xpdf suggests no packages.
-- no debconf information
Reply to: