Bug#1023659: gscan2pdf: can't use unpaper as it gives errors

[Francesco Potortì]

Package: gscan2pdf
Version: 2.13.0-1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì <Pot...@isti.cnr.it>

If I enable the "Postprocessing / Clean up images" option with default values, I get errors from unpaper. Here they are:

[image2 @ 0x564ee7da3540] Encoder did not produce proper pts, making some up.
[image2 @ 0x564ee7da3540] The specified filename '/tmp/gscan2pdf-EBri/SGOfFcr2Nn.pnm' does not contain an image sequence pattern or a pattern is invalid.
[image2 @ 0x564ee7da3540] Use a pattern such as %03d for an image sequence or use the -update option (with -frames:v 1 if needed) to write a single image.

The file mentioned in the second of the three error messages does not exist.

This is unpaper 7.0.0-0.1

If I downgrade to unpaper 6.1-2+b2 I get these errors instead:

[ppm_pipe @ 0x5560cbcbd500] Stream #0: not enough frames to estimate rate; consider increasing probesize
[image2 @ 0x5560cbcc3740] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
[image2 @ 0x5560cbcc3740] Encoder did not produce proper pts, making some up.

I can't downgrade unpaper further because that would require installing old dependencies.

I have used gscan2pdf (with unpaper) for many years, and I am sure it used to work without problems until maybe one year ago. I also tried downgrading gscan2pdf to 2.3.0-1, the error message changes but it is always there.


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gscan2pdf depends on:
ii imagemagick 8:6.9.11.60+dfsg-1.3+b4
ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3+b4
ii libconfig-general-perl 2.65-2
ii libdate-calc-perl 6.4-2
ii libfilesys-df-perl 0.92-7+b1
ii libgoocanvas2-perl 0.06-3
ii libgtk3-imageview-perl 10-1
ii libgtk3-perl 0.038-2
ii libgtk3-simplelist-perl 0.21-1
ii libhtml-parser-perl 3.79-1+b1
ii libimage-magick-perl 8:6.9.11.60+dfsg-1.3
ii libimage-sane-perl 5-1+b3
ii liblist-moreutils-perl 0.430-2
ii liblocale-codes-perl 3.72-1
ii liblocale-gettext-perl 1.07-4+b3
ii liblog-log4perl-perl 1.57-1
ii libossp-uuid-perl [libdata-uuid-perl] 1.6.2-1.5+b11
ii libpdf-builder-perl 3.024-1
ii libproc-processtable-perl 0.634-1+b2
ii libreadonly-perl 2.050-3
ii librsvg2-common 2.54.5+dfsg-1
ii libset-intspan-perl 1.19-3
ii libtiff-tools 4.4.0-5
ii libtry-tiny-perl 0.31-2
ii sane-utils 1.1.1-6+b1

Versions of packages gscan2pdf recommends:
ii djvulibre-bin 3.5.28-2
ii gocr 0.52-5
ii pdftk 2.02-5+b1
ii pdftk-java [pdftk] 3.3.2-1
ii tesseract-ocr 5.1.0-2
ii unpaper 7.0.0-0.1
ii xdg-utils 1.1.3-4.1

gscan2pdf suggests no packages.

-- no debconf information

[Jeff]

On 08/11/2022 15:06, Francesco Potortì wrote:
> If I enable the "Postprocessing / Clean up images" option with default values, I get errors from unpaper. Here they are:
>
> [image2 @ 0x564ee7da3540] Encoder did not produce proper pts, making some up.
> [image2 @ 0x564ee7da3540] The specified filename '/tmp/gscan2pdf-EBri/SGOfFcr2Nn.pnm' does not contain an image sequence pattern or a pattern is invalid.
> [image2 @ 0x564ee7da3540] Use a pattern such as %03d for an image sequence or use the -update option (with -frames:v 1 if needed) to write a single image.
>
> The file mentioned in the second of the three error messages does not exist.

I think that these are warnings, not errors, as I get output from
unpaper despite them.

Because of errors/warnings like this, the message window that displays
them gives you the possibility to hide them in the future. This works
for the first and third messages, but not the second (because the
filename changes every time).

I could take a look at the logic that parses the messages and see if I
improve it.

However, I'm not sure there is any point, as I see this bug report:

https://github.com/unpaper/unpaper/issues/113

which is fixed by this commit:

https://github.com/unpaper/unpaper/commit/a2a88fe837fd6770ac94f08b2eb841f0dc9d2430

So I am tempted to reassign this to unpaper.

[Jeff]

reassign 1023659 unpaper 7.0.0-0.1
thanks

[Francesco Potortì]

The problem is, it is okay to ignore a warning once one knows that in fact it is not really a problem.

But I usually try to not ignore warnings if I do not know what they mean...