On 9/17/07, Mike Hommey <[EMAIL PROTECTED]> wrote: > Try something like strace -eopen -f update-mime-database 2>&1 | grep libz.so > and check where libz.so is taken from. > If it's not taken in /usr/lib or /lib, then you're likely to have a > broken LD_LIBRARY_PATH and/or a spurious libz.so somewhere else.
$ strace -eopen -f update-mime-database 2>&1 | grep libz.so open("/usr/local/lib/libz.so.1", O_RDONLY) = 3 $ echo $LD_LIBRARY_PATH [empty] $ ls /usr/local/lib/libz.so.1 -l lrwxrwxrwx 1 root staff 13 2007-03-03 07:09 /usr/local/lib/libz.so.1 -> libz.so.1.2.3 $ ls /usr/lib/libz.so.1 -l lrwxrwxrwx 1 root root 15 2007-07-16 13:28 /usr/lib/libz.so.1 -> libz.so.1.2.3.3 There is also a directory called /usr/local/lib/site_ruby which holds the ruby gems stuff, so I'm guessing this issue is somehow related to installing ruby gems and *not* using apt (apt gems is broken, but I digress). So, it appears this issue may be my fault, but I'm clueless as to how to fix it. This link warns against setting $LD_LIBRARY_PATH: http://linuxmafia.com/faq/Admin/ld-lib-path.html Should I set the soft link at /usr/local/lib/libz.so.1 to point to /usr/lib/libz.so.1.2.3.3 (seems a tenuous solution)? How would installing ruby gems have caused gnome programs to prefer /usr/local/lib over /usr/lib ? How can I reverse that effect? Thanks, I really appreciate your time. -- Justin M. Keyes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]