I have a 32-bit Lucid installation here.
My solution was to rename 
/lib/libnss_files.so.2 and
/lib/tls/i686/cmov/libnss_files.so.2

Now I can use the scanner, but I do get one more error:
netdiscovery: relocation error: /lib/tls/i686/cmov/libresolv.so.2: symbol 
strlen, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

Details follow:

# uname -a
Linux biser 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:12:52 UTC 2010 i686 
GNU/Linux
# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS"

# /opt/Samsung/mfp/bin/Configurator
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
netdiscovery: relocation error: /lib/tls/i686/cmov/libnss_files.so.2: symbol 
strcmp, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
netdiscovery: relocation error: /lib/tls/i686/cmov/libnss_files.so.2: symbol 
strcmp, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
# cd /lib/tls/i686/cmov/
# mv libnss_files.so.2 libnss_files.so.2.bkp
# /opt/Samsung/mfp/bin/Configurator
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
netdiscovery: relocation error: /lib/libnss_files.so.2: symbol strcmp, version 
GLIBC_2.0 not defined in file libc.so.6 with link time reference
netdiscovery: relocation error: /lib/libnss_files.so.2: symbol strcmp, version 
GLIBC_2.0 not defined in file libc.so.6 with link time reference
# cd /lib
# mv libnss_files.so.2 libnss_files.so.2.bkp
# /opt/Samsung/mfp/bin/Configurator
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
netdiscovery: relocation error: /lib/tls/i686/cmov/libresolv.so.2: symbol 
strlen, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
(now I can actually see and use the scanner!!!)

-- 
netdiscovery: relocation error & segfault
https://bugs.launchpad.net/bugs/576531
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to