http://qa.mandrakesoft.com/show_bug.cgi?id=1640
------- Additional Comments From [EMAIL PROTECTED] 2003-02-07 17:27 -------
Bug is still present in sane-1.0.11-6mdk.src.rpm rebuilt for slightly cooked
9.1 system. (I don't have disk space or bandwidth to maintain a full-blown
cooker installation.) It can be confirmed even without a Visioneer scanner
being present on the system by the following steps:
1) As root, create /etc/sane.d/viceo.conf if not already present (not included
in rpm). It should contain the single line "/dev/usb/scanner0". Since the
backend will fail to dlopen, I don't believe it matters whether anything is
actually connected to that device.
2) As root, set debug to maximum.
export SANE_DEBUG_DLL=128
export SANE_DEBUG_VICEO=128
3) As root,
scanimage -L 2>&1 | grep viceo
4) The output will be:
[dll] add_backend: adding backend `viceo'
[dll] load: searching backend `viceo' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-viceo.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-viceo.so.1'
[dll] load: dlopen() failed (/usr/lib/sane/libsane-viceo.so.1:
undefined symbol: __gxx_personality_v0)
As mentioned in earlier report, this is listed in the FAQ at
http://viceo.orcon.net.nz/ which points the finger at gcc 3.2. Additional
research suggested that gcc 3.2 didn't automatically run C++ as needed the way
older versions did. Since I only scan about once a month, I haven't pursued the
subject any further.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
Using Visioneer OneTouch 7600 USB scanner, I get the following:
scanimage -L
[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.8 from sane-backends
1.0.10
[dll] add_backend: adding backend `viceo'
[dll] load: searching backend `viceo' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-viceo.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-viceo.so.1'
[dll] load: dlopen() failed (/usr/lib/sane/libsane-viceo.so.1: undefined
symbol: __gxx_personality_v0)
This is listed in the FAQ at http://viceo.orcon.net.nz/ . It points the
finger at gcc 3.2. Further research suggested that gcc 3.2 didn't
automatically run C++ the way older versions did. I don't know
how valid that explanation is, but I thought it was worth passing
along.
