Oliver Schwartz wrote:
Hi,
http://www.linuxprinting.org/till/tmp/eps2480debug.log
http://www.linuxprinting.org/till/tmp/eps2580debug.log
[snapscan] sense_handler: Hardware error. (0x00, 0x04)
according to my docs this means scan module locked. You probably
didn't remove the
Till Kamppeter wrote:
---
SANE_DEBUG_SNAPSCAN=255 xsane eps2480_3debug.log 21
---
Successful run of xsane. Nothing than one pre-scan of the full scanning
Hi,
Thanks, on the 2480 this was really the case. On the 2580 it was
already open.
It seems the 2580 behaves somewhat different, although it uses the
same USB ID. Up to now I have no idea what's going wrong.
The log you sent for the 2580 indicates an error in
snapscani_usb_open() which is
Oliver Schwartz wrote:
It seems the 2580 behaves somewhat different, although it uses the
same USB ID. Up to now I have no idea what's going wrong.
The log you sent for the 2580 indicates an error in
snapscani_usb_open() which is only a small wrapper for
sanei_usb_open(). Can you provide
Oliver Schwartz wrote:
The delays are annoying, but it seems that all delays are requested by
the scanner. You can try to reduce the number of retries for the
test_unit_ready in snapscan-scsi.c, line 1008 and see if that works
any better.
Would this really help? The scanners are USB
Oliver Schwartz wrote:
On all later attempts I got a segmentation fault when the GUI
started to open. The command line was the following:
There's nothing obvious in the log. Can you run xsane in gdb and
create a stacktrace (command bt IIRC) after the crash?
/Oliver
Here is a
Oliver Schwartz wrote:
Hi,
Thanks, on the 2480 this was really the case. On the 2580 it was
already open.
It seems the 2580 behaves somewhat different, although it uses the
same USB ID. Up to now I have no idea what's going wrong.
The log you sent for the 2580 indicates an error in
Hi Henning,
Henning Meier-Geinitz wrote:
Feature freeze for sane-backends 1.0.15 is now active. That means,
that now new backend or new features for existing backends should be
committed to CVS. Bug fixes, documentation and translation updates are
ok.
Timetable:
2004-10-31 Code freeze
On Wednesday 20 October 2004 02.00, Till Kamppeter wrote:
Oliver Schwartz wrote:
The delays are annoying, but it seems that all delays are
requested by the scanner. You can try to reduce the number of
retries for the test_unit_ready in snapscan-scsi.c, line 1008 and
see if that works any
Hi,
On Wed, Oct 20, 2004 at 08:19:41AM +0200, René Rebe wrote:
I have some more avision updates in the queue, mostly fixes and cleanups
- but also the button readout code, which would be a new feature ...
Should I leave it out and seperate the rest of the code, or are those
few button code
Impossible, I have installed SANE always by RPM, for a new version I
have rebuilt the RPM on the compiling machine and then updated the RPM
on my testing machine.
Till
Oliver Schwartz wrote:
Hi,
the backtraces are quite obscure. Is there any chance that you have
two versions of SANE
Hi,
On Wed, Oct 20, 2004 at 12:21:34AM +0200, Oliver Schwartz wrote:
There's nothing obvious in the log. Can you run xsane in gdb and
create a stacktrace (command bt IIRC) after the crash?
Why does the frontend want to set the gray gamma table to (nil)?
[snapscan]
12 matches
Mail list logo
