On 05/14/2010 10:40 AM, Grant wrote:
Thank you for writing. I'd love to be able to fix this. Is Image
Scan! synonymous with the epkowa backend?
Image Scan! is a frontend for exclusive use with the epkowa backend. It is
developed in tandem with the epkowa backend and available on the Avasys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grant :
I've had a scan server set up for a while which uses saned via xinetd.
Is there a simpler way to set up a scan server with fewer permissions
to grant? The configuration seems a lot more complex than my printer
server which has
On 05/14/2010 02:33 PM, Grant wrote:
I tried a few different frontends including Image Scan and they all
produced the same horizontal lines. Increasing the scan resolution
from 300dpi to 600dpi prevents the lines from appearing, but Image
Scan is the only frontend I've found that makes 600dpi
I'm sorry. I forgot to mention the version. 'scanimage --version' gives me
'scanimage (sane-backends) 1.0.20; backend version 1.0.20'.
I now noticed that there is a support page for each version which I didn't see
at all before. Obviously, I need to search for my scanner in
It is possibly just a permissions issue. Try it as root. If that
works, then we have to update udev/hal rules
allan
On Fri, May 14, 2010 at 6:00 AM, kltrg m.kltrg at googlemail.com wrote:
I'm sorry. I forgot to mention the version. 'scanimage --version' gives me
'scanimage (sane-backends)
It is possibly just a permissions issue. Try it as root. If that
works, then we have to update udev/hal rules
'sudo scanimage -L' doesn't work either, so it seems not to be a permission
issue.
Try this:
SANE_DEBUG_EPSON2=255 scanimage -L
and lets see what that gives.
oh- and is it possible that the updated sane version failed to update
the contents of /etc/sane.d? those config files must match the running
version of sane...
allan
On Fri, May 14, 2010 at 6:44 AM, kltrg m.kltrg at
Try this:
SANE_DEBUG_EPSON2=255 scanimage -L
It gives me:
:~$ SANE_DEBUG_EPSON2=255 scanimage -L
[sanei_debug] Setting debug level of epson2 to 255.
[epson2] sane_epson2_init: sane-backends 1.0.21cvs
[epson2] epson2 backend, version 1.0.124
[epson2] sane_epson2_get_devices
[epson2]
try adding this string to /etc/sane.d/epson2.conf:
usb 0x04b8 0x0851
allan
On Fri, May 14, 2010 at 6:55 AM, kltrg m.kltrg at googlemail.com wrote:
Try this:
SANE_DEBUG_EPSON2=255 scanimage -L
It gives me:
:~$ SANE_DEBUG_EPSON2=255 scanimage -L
[sanei_debug] Setting debug level of epson2
I added the line and now I get:
:~$ scanimage -L
device `epson2:libusb:002:008' is a Epson PID 0851 flatbed scanner
This sounds good and xsane and gscan2pdf recognize the scanner but I still
can't scan. I always get an error message: 'Failed to start scanner: Operation
not supported'.
Try it with the DEBUG flag I gave before...
allan
On Fri, May 14, 2010 at 8:07 AM, kltrg m.kltrg at googlemail.com wrote:
I added the line and now I get:
:~$ scanimage -L
device `epson2:libusb:002:008' is a Epson PID 0851 flatbed scanner
This sounds good and xsane and gscan2pdf recognize
I get this: http://pastebin.com/uG81XyKn
Am 14.05.2010 14:40, schrieb m. allan noah:
Try it with the DEBUG flag I gave before...
allan
On Fri, May 14, 2010 at 8:07 AM, kltrg m.kltrg at googlemail.com wrote:
I added the line and now I get:
:~$ scanimage -L
device `epson2:libusb:002:008'
well, that looks good, do the same when trying to scan:
SANE_DEBUG_EPSON2=255 xsane 2xsane.log
go until it gives you an error, and send the log here (compress it if large)
allan
On Fri, May 14, 2010 at 11:41 AM, kltrg m.kltrg at googlemail.com wrote:
I get this: http://pastebin.com/uG81XyKn
'.
-- next part --
A non-text attachment was scrubbed...
Name: xsane.log
Type: text/x-log
Size: 62394 bytes
Desc: not available
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100514/2e16a95d/attachment-0001.bin
I dont see any problems in this file. Are you sure it was not truncated?
allan
On Fri, May 14, 2010 at 12:46 PM, kltrg m.kltrg at googlemail.com wrote:
I attached the logfile to the mail.
Thanks for all you efforts! kltrg
Am 14.05.2010 18:01, schrieb m. allan noah:
well, that looks good,
If anybody has any ideas, I'd love to hear them. Otherwise I will
return the scanner to the store. scanimage fails even when run
as root. thanks, -kurt
- Forwarded message from Kurt Rosenfeld hardware at
ees1s0.engr.ccny.cuny.edu -
Date: Wed, 12 May 2010 22:30:47 -0400
From: Kurt
Hi folks,
as various distros still have to maintain a lot of patches against
sane, the following paper might be of your interest ...
http://www.metux.de/download/oss-qm-project-2010050101.pdf
cu
--
-
Enrico Weigelt==
I don't know the answer but probably the failure is related to this
part of the log file:
[epson2] using built in CCT profile
[epson2] esci_set_color_correction_coefficients
[epson2] esci_set_color_correction_coefficients: not supported
What version of sane-backends are you running? Looking at
I tried a few different frontends including Image Scan and they all
produced the same horizontal lines. ?Increasing the scan resolution
from 300dpi to 600dpi prevents the lines from appearing, but Image
Scan is the only frontend I've found that makes 600dpi available.
xsane and xscanimage
I've had a scan server set up for a while which uses saned via xinetd.
?Is there a simpler way to set up a scan server with fewer permissions
to grant? ?The configuration seems a lot more complex than my printer
server which has only cupsd.conf config on the server and client.conf
config on
Thanks for responding. Here is a log of scanimage
run as root in Linux, without the -T:
http://isis.poly.edu/~kurt/scanimage_debuglevel_21.txt
sane-find-scanner consistently finds the scanner.
I am running it in native Linux and native FreeBSD (two
separate boxes, both running sane-backends
21 matches
Mail list logo
