Hi,

On Sun, Sep 11, 2005 at 12:38:17PM -0400, Carlos Moffat wrote:
> It a coolscan 4000. I believe the backend is sane-coolscan2

Right. The crash seems to happen in coolscan (not coolscan2) however.
The backtrace looks more like sane-coolscan.

> Program received signal SIGSEGV, Segmentation fault.
> 0xb708284b in sane_coolscan_get_select_fd () from 
> /usr/lib/sane/libsane-coolscan.so.1
> (gdb) bt
> #0  0xb708284b in sane_coolscan_get_select_fd () from 
> /usr/lib/sane/libsane-coolscan.so.1
> #1  0xb7088889 in sanei_scsi_find_devices () from 
> /usr/lib/sane/libsane-coolscan.so.1

This is quite strange. get_select_fd shouldn't be called during
sane_init. Something is completely wrong here. The direct cause auf
the segfault is that sane_coolscan_get_select_fd gets called with an
invalid handle argument.

Maybe coolscan tries to attach the scanner and gets confused somehow?

Could you send the output of:
SANE_DEBUG_COOLSCAN=255 xsane

As a workaround, you could diable (comment out) "coolscan" in
/etc/sane.d/dll.conf.

Bye,
  Henning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to