[sane-devel] multiple images on XSane
F J Brooks
F J Brooks" <fred@redgrave.screaming.net
Mon, 9 Jun 2003 06:42:08 +0100
On Sat, 31 May 2003 09:15:11 +0200, Henning Meier-Geinitz
<henning@meier-geinitz.de>
wrote:
> So an older version of xsane works? The current version is 0.91, by
> the way.
Is there any advantage to me in installing xsane 0.91, eg, will it solve my
current problems? I installed v.0.90 only two or three weeks ago (when it
was then the latest).
> Which version of sane-backends do you use?
The version of sane-backends (and sane-frontends) I have is 1.0.11.
> Does it depend on resolution or mode setting? Only in viewer mode or
> also in the preview window and when you save the image?
It doesn't depend on mode, in that I get the same result in the viewer
window, when I copy/print, and if I save the image to file and then print.
The preview window doesn't seem to work in that it shows a dark, hatched
strip about 3 cm wide across the top of the window, with the rest of the
window area (A4) white.
> Different speed are rather uncommon when using different frontends. Are
> you sure that you have only one version of sane-backends installed?
No, I found that I also had sane-backends-1.0.8 [the original which came
with my SuSE distribution]. So I removed it (using YaST2). That's when
things got even worse!
I found that, when I clicked on my desktop scanner icon to open
/usr/local/bin/xsane, I got the error message:
'Sorry - KDesktop: KDEInit could not launch '/usr/local/bin/xsane'.
When I tried the same thing using Konqueror, I got the error message:
'Error - Konqueror: Unable to run the command specified. The file or
directory file: /usr/local/bin/xsane does not exist.'
I found this rather surprising so I tried:
fredjb@FJBrooks:~> ls -l /usr/local/bin
total 5281
-rwxr-xr-x 1 root root 20461 2003-05-18 14:18
gamma4scanimage
-rwxr-xr-x 1 root root 2255362 2003-06-0509:39 gimp
drwxr-xr-x 11 root root 2464 2003-06-05 17:01 glib-2.2.1
-rwxr-xr-x 1 root root 68062 2003-05-10 16:30
glib-genmarshal
-rwxr-xr-x 1 root root 4650 2003-05-10 16:29
glib-gettextize
-rwxr-xr-x 1 root root 13446 2003-05-10 16:30 glib-mkenums
-rwxr-xr-x 1 root root 58018 2003-05-10 16:30
gobject-query
drwxr-xr-x 14 root root 1688 2003-06-05 17:02 gtk+-2.2.1
-rwxr-xr-x 1 root root 380652 2003-05-10 15:39 pkg-config
drwxr-xr-x 4 root root 1664 2003-06-05 17:04
pkgconfig-0.15.0
-rwxr-xr-x 1 root root 1469115 2003-05-20 16:52 quiteinsane
drwxr-xr-x 4 root root 1008 2003-06-05 16:58
quiteinsane-0.10
drwxr-xr-x 12 root root 1696 2003-06-05 16:59
sane-backends-1.0.11
-rwxr-xr-x 1 root root 3298 2003-05-18 14:18 sane-config
-rwxr-xr-x 1 root root 141103 2003-05-18 14:18
sane-find-scanner
drwxr-xr-x 7 root root 816 2003-06-05 17:00
sane-frontends-1.0.11
-rwxr-xr-x 1 root root 67552 2003-05-12 09:46 scanadf
-rwxr-xr-x 1 root root 102425 2003-05-18 14:18 scanimage
-rwxr-xr-x 1 root root 305145 2003-05-12 09:46 xcam
drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90
-rwxr-xr-x 1 root root 478145 2003-05-12 09:46 xscanimage
fredjb@FJBrooks:~>
[Many of these were recently downloaded from their source sites on the net,
to
replace older, out-of-date versions.]
To see what the general position was, I then tried:
fredjb@FJBrooks:~> sane-find-scanner
found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/scanner
found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/sg2
# Your SCSI scanner was detected. It may or may not be supported by
SANE. Try
# scanimage -L and read the backend's manpage.
# No USB scanners found. If you expected something different, make
sure that
# you have loaded a driver for your USB host controller and have
installed a
# kernel scanner module.
# Scanners connected to the parallel port or other proprietary ports
can't be
# detected by this program.
# You may want to run this program as root to find all devices. Once
you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
Followed by:
fredjb@FJBrooks:~> scanimage -L
device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed
scanner
device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed
scanner
fredjb@FJBrooks:~>
I then tried [I have extracted only the bits I thought relevant to my
scanner]:
SANE_DEBUG_DLL=255 scanimage -L
[sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend version 1.0.8 from sane-backends
1.0.11
[dll] add_backend: adding backend `net'
[dll] add_backend: adding backend `abaton'
[dll] add_backend: adding backend `agfafocus'
[dll] add_backend: adding backend `apple'
[dll] add_backend: adding backend `avision'
[dll] add_backend: adding backend `artec'
[...................]
[dll] add_backend: adding backend `umax1220u'
[dll] add_backend: adding backend `v4l'
[dll] load: searching backend `v4l' in `/usr/local/lib/sane'
[dll] load: trying to load `/usr/local/lib/sane/libsane-v4l.so.1'
[dll] load: dlopen()ing `/usr/local/lib/sane/libsane-v4l.so.1'
[dll] init: initializing backend `v4l'
[dll] init: backend `v4l' is version 1.0.2
[dll] load: searching backend `umax1220u' in `/usr/local/lib/sane'
[........................]
[dll] init: backend `artec' is version 1.0.0
[dll] load: searching backend `avision' in `/usr/local/lib/sane'
[dll] load: trying to load `/usr/local/lib/sane/libsane-avision.so.1'
[dll] load: dlopen()ing `/usr/local/lib/sane/libsane-avision.so.1'
[dll] init: initializing backend `avision'
[dll] init: backend `avision' is version 1.0.55
[dll] load: searching backend `apple' in `/usr/local/lib/sane'
[.......................]
[dll] load: searching backend `net' in `/usr/local/lib/sane'
[dll] load: trying to load `/usr/local/lib/sane/libsane-net.so.1'
[dll] load: dlopen()ing `/usr/local/lib/sane/libsane-net.so.1'
[dll] init: initializing backend `net'
[dll] init: backend `net' is version 1.0.11
device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed
scanner
device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed
scanner
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `v4l's exit function
[......................]
[dll] sane_exit: calling backend `artec's exit function
[dll] sane_exit: calling backend `avision's exit function
[dll] sane_exit: calling backend `apple's exit function
[dll] sane_exit: calling backend `agfafocus's exit function
[dll] sane_exit: calling backend `abaton's exit function
[dll] sane_exit: calling backend `net's exit function
[dll] sane_exit: finished
fredjb@FJBrooks:~>
> What happens if you scan with scanimage? E.g. "scanimage >image.pnm".
> Or xscanimage?
Tried: fredjb@FJBrooks:~> scanimage >image.pnm
Scanner whirred quietly for a while, but no other response.
Then tried: xscanimage:
Got 'Select Device' panel giving choice:
'avision:/dev/scanner
avision:/dev/sg2
Chose former, clicked 'OK', got: avision/dev/scanner window, on which
clicked: 'Preview Window'. Got Preview Window, dragged dashed line into
rectangle covering roughly A4 size, then clicked 'Acquire Preview'.
Scanner made fairly loud scratching-type noise plus hum, then
intermittent whirring noise.
Nothing appeared in Preview Window, and 'Acquire Preview' button
reappeared.
Clicked 'Scan' on main window. After a minute or two, scanner started with
whirring noise, and got 'Scanning' panel with 'Receiving RGB data for
out.pnm' progress bar graphic. Also second panel headed: 'Output Filename',
listing directories and files.
After ten-plus minutes, scanning seems complete and 'Scanning' panel
disappears. Open out.pnm file and get colour image of object, slightly
distorted as is longer and thinner than original.
So that's where I am, Henning - as you can see, in rather a mess. Anything
you
can do to resolve the situation would be much appreciated.
Thanks
Best
Fred