Your message dated Thu, 26 Jul 2007 01:20:40 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434018: gscan2pdf: Unknown message: scanimage: attempted
to set inactive option brightness
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gscan2pdf
Version: 0.9.14
Severity: important
As recently as a few weeks ago, my scanner used to work with
'gscan2pdf':
% lsscsi | grep scan
[0:0:5:0] scanner UMAX UMAX S-6E V2.0 -
...but now when I scan anything, it fails.
'gscan2pdf --debug' outputs:
{...stuff deleted.}
scanimage --device-name='umax:/dev/sg1' --mode='Lineart' --source='Flatbed'
-y 279.4 -l 0 --brightness='0' --threshold='50' --resolution='300' -x 215.788
-t 0 --batch --batch-count=1
Forked PID 5345
Unknown message: scanimage: attempted to set inactive option brightness
Waiting to reap process at /usr/bin/gscan2pdf line 2751.
Reaped PID 5345
Apparently it sends an inappropriate "--brightness='0'" option, (maybe
there's no such thing for this scanner), to 'scanimage', which fails.
Downgrading to v0.9.10-1 fixes the problem, since it has no 'brightness'
option.
It's not obvious what's the best way to fix this bug. Ideally
'gscan2pdf' should somehow know enough about the scanner its calling
before it invokes 'scanimage'. If for some reason that's not feasible
then it could check for the above error -- perhaps during some hardware
initialization routine: scan a little patch, send the data to /dev/null,
and grep the standard error output helpful errors, after which it would
then know not to use certain options on certain scanners.
Hope this helps...
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages gscan2pdf depends on:
ii libglib-perl 1:1.144-1 Perl interface to the GLib and GOb
ii libgtk2-ex-simple-l 0.50-1 A simple interface to Gtk2's compl
ii libgtk2-perl 1:1.140-1 Perl interface to the 2.x series o
ii liblocale-gettext-p 1.05-1 Using libc functions for internati
ii libpdf-api2-perl 0.61-1 provides the functions for creatin
ii libsane 1.0.19~cvs20070505-3 API library for scanners
ii libtiff-tools 3.8.2-7 TIFF manipulation and conversion t
ii perlmagick 7:6.2.4.5.dfsg1-1 A perl interface to the libMagick
ii sane-utils 1.0.19~cvs20070505-3 API library for scanners -- utilit
Versions of packages gscan2pdf recommends:
ii djvulibre-bin 3.5.19-2 Utilities for the DjVu image forma
ii gocr 0.41-1 A command line OCR
ii libgtk2-ex-podviewer-perl 0.14-2.1 Perl Gtk2 widget for displaying Pl
ii sane 1.0.14-2 scanner graphical frontends
pn tesseract-ocr <none> (no description available)
ii unpaper 0.2-2 post-processing tool for scanned p
ii xdg-utils 1.0.1-2 Desktop integration utilities from
-- debconf-show failed
--- End Message ---
--- Begin Message ---
On Wed, 25 Jul 2007 13:54:54 +0200
"Jeffrey Ratcliffe" <[EMAIL PROTECTED]> wrote:
> Thanks for the output. In the meantime, I have released v0.9.15, which
> I believe fixes this problem.
Just fetched and tested v0.9.15, it works again, and for the fix &
rapid turnaround I hereby gratefully close now this here ex-bug that
crawls no more.
--- End Message ---
