[sane-devel] old Agfa DuoScan / Floating point exception

Sun Apr 16 15:21:40 UTC 2006

Am Sonntag, 16. April 2006 16:17 schrieb Frank Zago:

thanks Frank, for your advice

> First you have to uninstall sane-backend. Something such as "rpm -e
> --nodeps sane-backends" should do.

it seems (to me) that on SUSE 10.0 things are named a bit different???:
"which sane-backends" gave nothing, so rpm -e... didn't result in anything, of 
course, too
I used Yast (Suse install-tool) to uninstall the sane rpm
>
> Then download the sane-backends from sane-project.org.
>
> Untar in a suitable place, then type the usual "./configure", "make" and
> as root "make install".

when I first typed ./configure I saw that it will install in /usr/local but I 
felt, that Suse uses other directories. After googling a while I used the 
following:

./configure --mandir=/usr/man --libdir=/usr/lib --prefix=/usr 
--sysconfdir=/etc

hope that's ok. As far as I can interpret it, configure, make and make install 
went fine (however I have all the output in text-files, if needed...)
>
> You  should then be able to do the same (failing) test again and get the
> same results.

not exactly, the differences are:
- the scanner is not detected anymore from a user prompt now (I've read about 
that somewhere and will search again later, I guess this is not the main 
problem)
- as root the floating point exception doesn't appear anymore, but the sanner 
is "found twice":

# scanimage -L
...
[microtek] ========== Congratulations! ==========
...
[microtek]  === SANE/Microtek backend v0.13.1 ===
[microtek] ========== Scanner Inquiry Block ========mm
[microtek] 06 36 16 01 5b 00 00 00 41 47 46 41 20 20 20 20
[microtek] 44 55 4f 53 43 41 4e 20 20 20 20 20 20 20 20 20
[microtek] 31 2e 36 30 53 43 53 49 20 46 57 20 56 33 2e 36
[microtek] 20 43 54 4c 35 33 38 30 03 4f 8c c5 06 ee 5d 43
[microtek] 01 03 47 00 00 83 00 01 0e 4a 07 05 00 00 00 00
[microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
[microtek] ========== Scanner Inquiry Report ==========
[microtek] ===== Scanner ID...
[microtek] Device Type Code: 0x06
[microtek] Model Code: 0x5d
[microtek] Vendor Name: 'AGFA    '   Model Name: 'DUOSCAN         '
[microtek] Vendor Specific String: 'SCSI FW V3.6 CTL5380'
[microtek] Firmware Rev: '1.60'
[microtek] SCSI F/W version: 3.6     Scanner F/W version: 1.6
[microtek] Response data format: 0x01
[microtek] ===== Imaging Capabilities...
[microtek] Modes:  Lineart Halftone Gray Color (OnePass)
[microtek] Resolution Step Sizes: 1% 5%    Expanded Resolution Support? yes
[microtek] Supported Bits Per Sample: 4 8 10 12
[microtek] Max. document size code: 0x06
[microtek] Max. document size:  8299 x 13499 pixels
[microtek] Frame units:  pixels  1/8"'s
[microtek] # of built-in halftones: 12   Downloadable patterns? Yes
[microtek] Data Compression:
[microtek] Contrast Settings: 14   Exposure Settings: 74
[microtek] Adjustable Shadow/Highlight? yes   Adjustable Midtone? yes
[microtek] Digital brightness/offset? yes
[microtek] Gamma Table Size: 4096 entries of 2 bytes (max. depth: 12)
[microtek] ===== Source Options...
[microtek] Feed type:  flatbed    ADF support? yes
[microtek] Document Feeder Support? yes   Feeder Backtracking? yes
[microtek] Feeder Installed? no           Feeder Ready? no
[microtek] Transparency Adapter Installed? yes
[microtek] Fast Color Prescan? no
[microtek] Selectable Transfer Format? no
[microtek] Color Transfer Sequence: line-by-line, non-sequential with headers
[microtek] Three pass scan support? no
[microtek] ModeSelect-1 and ModeSense-1 Support? yes
[microtek] Can Disable Linearization Table? no
[microtek] Can Disable Start-of-Scan Recalibration? no
[microtek] Internal expanded expansion? no
[microtek] ====== End of Scanner Inquiry Report =======
device `snapscan:/dev/sg0' is a AGFA DUOSCAN flatbed scanner
device `microtek:/dev/sg0' is a Microtek Agfa DuoScan flatbed scanner

when I type "scanimage" alone (without -L or something) the scanner seems to 
go in it's basic position (I hear the "car" moving - sorry for my bad 
english...)

when I use Kooka (as root only, as a user Kooka doesn't see a scanner yet) 
then it crashes as before with same error:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
... repeated...
[Thread debugging using libthread_db enabled]
[New Thread 1098596480 (LWP 12646)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x41dd017d in sane_microtek_start (handle=0x82965c8) at microtek.c:4017
#7  0x413feb8e in sane_dll_start (handle=0x82936b8) at dll.c:1153
#8  0x413ffe5c in sane_start (h=0x82936b8) at dll-s.c:46
#9  0x401c1e76 in KScanDevice::acquire_data () 
from /opt/kde3/lib/libkscan.so.1
#10 0x401cba7c in KScanDevice::acquirePreview ()
   from /opt/kde3/lib/libkscan.so.1
#11 0x401cbf91 in ScanParams::slAcquirePreview ()
   from /opt/kde3/lib/libkscan.so.1
#12 0x401dbec9 in ScanParams::qt_invoke () from /opt/kde3/lib/libkscan.so.1
#13 0x40ceaa49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40ceaef0 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x4103454c in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40d7f306 in QButton::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x40d24708 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40c8ad41 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40c8bea8 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x4099760e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#21 0x40c25cd8 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40c24afb in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40c38bea in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40ca1c39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40ca1b36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40c8a68f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x0808118f in ?? ()
#28 0xbfa45de8 in ?? ()
#29 0xbfa45f00 in ?? ()
#30 0xbfa45ee8 in ?? ()
#31 0x08081020 in ?? ()
#32 0x00000006 in ?? ()
#33 0x40015ff4 in ?? () from /lib/ld-linux.so.2
#34 0x400166c4 in ?? ()
#35 0xbfa45e78 in ?? ()
#36 0xbfa45e8c in ?? ()
#37 0x4135bcd8 in main_arena () from /lib/tls/libc.so.6
#38 0x08147460 in ?? ()
#39 0x4135b8d8 in main_arena () from /lib/tls/libc.so.6
#40 0x00000002 in ?? ()
#41 0x00000020 in ?? ()
#42 0x40a3d908 in vtable for KApplication () 
from /opt/kde3/lib/libkdecore.so.4
#43 0x4135b8a0 in mp_ () from /lib/tls/libc.so.6
#44 0x081301f8 in ?? ()
#45 0x00000000 in ?? ()
#46 0x0812f700 in ?? ()
#47 0x08181040 in ?? ()
#48 0x0817fc08 in ?? ()
#49 0x081828a0 in ?? ()
#50 0x00000000 in ?? ()
#51 0x00000000 in ?? ()
#52 0x00000001 in ?? ()
#53 0x080a5438 in ?? ()
#54 0xbfa45e00 in ?? ()
#55 0x00000000 in ?? ()
#56 0x08187b40 in ?? ()
#57 0x08135418 in ?? ()
#58 0x08135988 in ?? ()
#59 0x00000000 in ?? ()
#60 0x40a3d984 in vtable for KApplication () 
from /opt/kde3/lib/libkdecore.so.4
#61 0x08132ed0 in ?? ()
#62 0x08136588 in ?? ()
#63 0x08147460 in ?? ()
#64 0x0809a808 in vtable for QCString ()
#65 0x08137f90 in ?? ()
#66 0xbfa45eb4 in ?? ()
#67 0x08140118 in ?? ()
#68 0x080a65a8 in ?? ()
#69 0x00000130 in ?? ()
#70 0x000001ff in ?? ()
#71 0x40fa9c4c in qt_check_pointer () from /usr/lib/qt3/lib/libqt-mt.so.3
#72 0x41253ea0 in __libc_start_main () from /lib/tls/libc.so.6
#73 0x08063511 in ?? ()
>
> After that we can move to the next stage.

Hope I did it ok until now and I am curious for the next step...

regards

Daniel