Hi
Allthough this bug is reported in 2009, I encounter today the same error
with my old Canon Canoscan 2700F connected with SCSI. I run Ubuntu 11.10
(64 bit) with the latest updates.
I included the backtrace:
Starting program: /usr/bin/xsane
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
sense_handler (scsi_fd=12, result=0x7edd80 <incomplete sequence \360>,
arg=<optimized out>) at canon.c:347
347 canon.c: No such file or directory.
in canon.c
(gdb) bt
#0 sense_handler (scsi_fd=12, result=0x7edd80 <incomplete sequence
\360>, arg=<optimized out>) at canon.c:347
#1 0x00007fffe5495228 in sanei_scsi_req_wait (id=0x7edd00) at
sanei_scsi.c:2411
#2 0x00007fffe549527a in sanei_scsi_cmd2 (fd=<optimized out>,
cmd=<optimized out>, cmd_size=<optimized out>, src=<optimized out>,
src_size=<optimized out>, dst=<optimized out>, dst_size=0x0) at
sanei_scsi.c:2480
#3 0x00007fffe5497440 in test_unit_ready (fd=12) at canon-scsi.c:55
#4 0x00007fffe5497a42 in attach (devnam=0x7fffffff7560 "/dev/sg4",
devp=0x0) at canon.c:698
#5 0x00007fffe5498841 in attach_one (dev=0x7fffffff7560 "/dev/sg4") at
canon.c:1798
#6 0x00007fffe5495a9b in sanei_scsi_find_devices (findvendor=0x7ec0b0
"CANON", findmodel=0x7eba90 "IX", findtype=0x0, findbus=-1,
findchannel=-1, findid=-1, findlun=-1, attach=0x7fffe5498820
<attach_one>) at sanei_scsi.c:3137
#7 0x00007fffe54935ac in sanei_config_attach_matching_devices
(name=<optimized out>, attach=0x7fffe5498820 <attach_one>) at
sanei_config2.c:142
#8 0x00007fffe5498d0a in sane_canon_init (version_code=<optimized out>,
authorize=<optimized out>) at canon-sane.c:82
#9 0x00007ffff7bd78d0 in init (be=0x73b5c0) at dll.c:613
#10 0x00007ffff7bd828d in sane_dll_get_devices (device_list=0x6a0b40,
local_only=0) at dll.c:1054
#11 0x00000000004711f5 in ?? ()
#12 0x0000000000476233 in ?? ()
#13 0x000000000040a3b4 in ?? ()
#14 0x00007ffff563130d in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#15 0x000000000040a4a1 in ?? ()
#16 0x00007fffffffe1d8 in ?? ()
#17 0x000000000000001c in ?? ()
#18 0x0000000000000001 in ?? ()
#19 0x00007fffffffe4ca in ?? ()
#20 0x0000000000000000 in ?? ()
(gdb)
Does this help you in finding a clue? If you need more info, let me know.
Mart
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
