[sane-devel] saned problems with 1.0.10-pre3 (incl. segfault)

Henning Meier-Geinitz henning@meier-geinitz.de
Tue, 28 Jan 2003 21:38:43 +0100


On Tue, Jan 28, 2003 at 12:25:42PM -0800, Lee Howard wrote:
> >Check permissions, i.e. if saned has read/write permissions on
> >/dev/usb/scanner0 .
> Thanks.  That was that.  The docs didn't mention anything about this, 

From man saned: "Note that both examples assume that there is a saned
Status: O

       group and a saned user.  If you follow this example, please
       make sure that the access permissions on the special device are
       set such that saned can access the scanner (the program
       generally needs read and write access to scanner devices)." :-)

> and the error message is misleading.

That's true. Well, at least it's not clear, beacuse SANE_STATUS_INVAL
means "some other error occured".

> It only des it when the permissions on /dev/usb/scanner0 are wrong.

So I assume it's a plustek problem even if I don't see any obvious bug.

> [dll] load: dlopen()ing `/usr/lib/sane/libsane-net.so.1'
> [dll] init: initializing backend `net'
> [dll] init: backend `net' is version 1.0.10
> Segmentation fault (core dumped)

Looks like it happens in sane_open. Please Try setting "export

> >Could you try to run saned in gdb directly? Maybe that gives more
> >information.
> I'm not a gdb expert.  How do I do this?

gdb saned
run -d128

Now start scanimage. When saned crahes, run bt to show the backtrace.