[sane-devel] xsane>0.91 crashes always with canon canoscan 2700F

Henning Meier-Geinitz henning@meier-geinitz.de
Tue, 11 May 2004 22:06:30 +0200


Hi,

On Wed, May 05, 2004 at 09:56:37PM +0200, Thomas Loescher wrote:
> Unfortunately, the last version of xsane wich worked together with my
> slide scanner (Canon canoscan 2700F, a scsi scanner) was 0.91. All
> version above this crashed when I choosed the scanner in the startup
> dialogue.

Does it work if you use a different backend? Try e.g. "xsane test". As
it works with mustke, it should also work with test but you never know.

> [dll] sane_get_option_descriptor(handle=0x8175798,option=6)
> [canon] >> sane_get_option_descriptor option number 6
> [canon]    sane_get_option_descriptor option name OPT_SCANNING_SPEED
> [canon] << sane_get_option_descriptor option number 6

Looks like that doesn't happen in the canon backend. 

> I also made an "strace xsane" (O.K. I really don't understand the
> output of strace, it's like chinese tome ;-),

It's just a list of the functions which have been called.

> but perhaps it helps
> somebody. I tried it with LANG=C and LANG=de_DE@euro, no diference it
> crashes in both ways

Did changing the locale have any effect at all (English/German texts
in xsane)? If not, try LC_ALL=C.

> open("/usr/share/locale/de_DE@euro/LC_MESSAGES/sane-backends.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/share/locale/de@euro/LC_MESSAGES/sane-backends.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/share/locale/de_DE/LC_MESSAGES/sane-backends.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/share/locale/de/LC_MESSAGES/sane-backends.mo", O_RDONLY) = 37
> fstat64(37, {st_mode=S_IFREG|0644, st_size=58618, ...}) = 0
> mmap2(NULL, 58618, PROT_READ, MAP_PRIVATE, 37, 0) = 0x410a5000
> close(37)                               = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Strange. Looks like it happened directly after loading the backend
translation file.

In addition to SANE_DEBUG_CANON=255 and SANE_DEBUG_DLL=255 you can
also set XSANE_DEBUG. Maybe that shows the exact position of the
problem.

Bye,
  Henning