[sane-devel] Problem with Iscan version iscan-2.19.0-4.c2

2009-05-18 Thread Olaf Meeuwissen
russbucket russbucket at nwi.net writes: On Thursday 14 May 2009 07:51:25 pm Olaf Meeuwissen wrote: russbucket russbucket at nwi.net writes: openSuSE 11.1 (2.6.27.21-0.1-default) KDE 4.2.1 release 106 libksane0-4.2.1-83.1 sane-backends-autoconfig-1.0.19-99.1 xsane-0.996-0.pm.1

[sane-devel] scanimage/scanadf Segmentation fault

2009-05-18 Thread Stefan Below
Hello, i have some troubles with scanimage. when try scanimage -L or scanimage --help, i get the following output: ... ., help message from scanimage . . Segmentation fault Thats it. gdb scanimage points me to: Program received signal SIGTRAP, Trace/breakpoint trap. 0x7f969c04d9e7 in ?? ()

[sane-devel] scanimage/scanadf Segmentation fault

2009-05-18 Thread m. allan noah
try: SANE_DEBUG_DLL=5 scanimage -L and lets see which backend the dll backend loads right before the problem. allan On Mon, May 18, 2009 at 11:16 AM, Stefan Below stefanbelow at gmx.de wrote: Hello, i have some troubles with scanimage. when try scanimage -L or scanimage --help, i get the

[sane-devel] scanimage/scanadf Segmentation fault

2009-05-18 Thread Stefan Below
hmm, thats strange. scanimage -L now works. Its a client / server setup. On client side i have a fujitsu-4120C2. When i try SANE_DEBUG_DLL=5 scanadf --mode Gray --compression JPEG The last lines are:[dll] sane_get_option_descriptor(handle=0x2240340,option=84) [dll]

[sane-devel] scanimage/scanadf Segmentation fault

2009-05-18 Thread m. allan noah
But on the server (where the scanner is connected) if you stop saned, you can scan with those arguments, correct? what if on the client side (no scanner) you scan without the --compression option? allan On Mon, May 18, 2009 at 11:37 AM, Stefan Below stefanbelow at gmx.de wrote: hmm, thats

[sane-devel] scanimage/scanadf Segmentation fault

2009-05-18 Thread Stefan Below
Its an ltsp environment, and i have not installed scanimagescanadf on the server side.Only saned is installed. Maybe i can do the testing in a few hours. I can scan with scanimage --mode Gray, but scanadf --mode Gray fgives me the seg fault. But thats a little bit strange.I got the same

[sane-devel] Fail to compile latest git

2009-05-18 Thread Nicolas Martin
Latest git compilation fails and drops at genesys backend. The same on 2 different Linux machines. Below, the beginning of the error message from make. Any idea ? Nicolas /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../include/sane -I/usr/local/include -I.

[sane-devel] Fail to compile latest git

2009-05-18 Thread stef
Le lundi 18 mai 2009 21:15:05 Nicolas Martin, vous avez ?crit : Latest git compilation fails and drops at genesys backend. The same on 2 different Linux machines. Below, the beginning of the error message from make. Any idea ? Nicolas /bin/bash ../libtool --silent --tag=CC

[sane-devel] SANE API evolution

2009-05-18 Thread stef
Hello, here are the features I think next revision of SANE's API should contain: There should be at least these user visible features: - new image formats such as jpeg - new frame types such a IR - warming up support - a way to tell user

[sane-devel] Problem with Iscan version iscan-2.19.0-4.c2

2009-05-18 Thread russbucket
On Monday 18 May 2009 12:08:32 am Olaf Meeuwissen wrote: russbucket russbucket at nwi.net writes: On Thursday 14 May 2009 07:51:25 pm Olaf Meeuwissen wrote: russbucket russbucket at nwi.net writes: openSuSE 11.1 (2.6.27.21-0.1-default) KDE 4.2.1 release 106 libksane0-4.2.1-83.1

[sane-devel] Can anyone tell me what's going on with this?

2009-05-18 Thread Mark Pemburn
Thanks Julien -- that did the trick! I had a real Doh! moment when I realized that this was exactly what was happening (over-writing the buffer with each call to sane_read). Once I set up a second buffer and appended the partial data to with each pass, I was finally able to see the whole