[SOLVED] Google Earth won't start on Slackware64 13.37 with multi-lib
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Google Earth won't start on Slackware64 13.37 with multi-lib
The problem, I can not get Google Earth to start on Slackware 64 bit system. This system I upgraded from 13.1, and I have Multi-lib support installed. I followed Alien Bob's doc to install Multi-lib.
There is one nagging question I have with the upgrade. Should I have deleted the /lib directory before re-installing multi-lib? I did not, I guessed the new versions of each file would overwrite the old versions.
Now, with some investigation, I can't make the symlink called for in the README,
Quote:
ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3
I ran the file command, and got this:
Quote:
file ld-lsb.so.3
ld-lsb.so.3: broken symbolic link to `/lib/ld-linux.so.2'
What I don't understand, is should there be a file ld-lsb.so.3 ? or a file ld-linux.so.2 ? I thought ( from what little I understand about symlinks, ) ld-lsb.so.3 should be a real file. Is that correct? If yes, what where do I get that file from?
If I have it backwards, where do I get ld-linux.so.2 from?
The symlink /lib/ld-lsb.so.3 -> /lib/ld-linux.so.2 is something that you have to do yourself.
I know, I tried. From what you have said, I'm missing the file ld-linux.so.2 Where do I get that from?
I removed the broken sym link. I re-ran the command 'upgradepkg --install-new *-compat32/*.t?z' from the slackware64-compat32 directory, however ld-linux.so.2 doesn't get installed.
When the command ran, I saw the message 'package skipped, already installed' So,
You get ld-2.13.so from glibc-2.13_multilib-x86_64-4alien and/or glibc-solibs-2.13_multilib-x86_64-4alien. Apparently you don't have ld-2.13.so, so apparently your multilib is broken.
You should only use installpkg, upgradepkg and removepkg (or the higher level tools like slackpkg and sbopkg) to install, upgrade/reinstall and remove packages. If you only use these tools, you will never need to delete anything manually. Especially not /lib ;-)
Well, progress of sorts. What I did was re-ran the install of compat32-tools. I then had ld-linux.so.2, which is a sym-link to ld-2.13.so. I made the sym-link as per the README for GoogleEarth.
I now see
Quote:
file /lib/ld-lsb.so.3
/lib/ld-lsb.so.3: symbolic link to `/lib/ld-linux.so.2'
Well, progress of sorts. What I did was re-ran the install of compat32-tools. I then had ld-linux.so.2, which is a sym-link to ld-2.13.so. I made the sym-link as per the README for GoogleEarth.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by camorri
The problem, I can not get Google Earth to start on Slackware 64 bit system. This system I upgraded from 13.1, and I have Multi-lib support installed. I followed Alien Bob's doc to install Multi-lib...
Where did you get the GoogleEarth package you are trying to run?
Once I had Slackware64 13.37 and the multilib files installed, I had trouble with the GoogleEarth package I had
previously downloaded from Google and ran on 'current.'
I went to GoogleEarth's web site and couldn't find a "generic" package, i.e., there was no longer (that I could find) a GoogleEarth.sh package, but only packages for .deb and .rpm. So, I went to SlackBuilds.org, download the script and the source, ran the script, and the resulting package installed and worked without a problem.
I went to GoogleEarth's web site and couldn't find a "generic" package, i.e., there was no longer (that I could find) a GoogleEarth.sh package, but only packages for .deb and .rpm. So, I went to SlackBuilds.org, download the script and the source, ran the script, and the resulting package installed and worked without a problem.
I got it from slackbuilds.org. It seg-faults.
Here is what is reported in dmesg.
Quote:
googleearth-bin[3083]: segfault at 729a3e4a ip 00000000f654bc96 sp 00000000ffdae708 error 6 in libGL.so.270.41.06[f64f3000+a1000]
It appears libGL.so.270.41.06 has something to do with it.
libGL.so.270.41.06 is part of Nvidia's binary driver which you seem to have installed. Perhaps try to install it (or a newer version) again? Make sure to answer "YES" to the question whether 32-bit driver should be installed as well.
Problem solved. I re-downloaded the driver from Nvidia, re-installed it from the new download, and said YES to 32 bit driver support. This is what I had done after the upgrade. Other 32 bit apps were O.K. specifically Frostwire worked like a charm.
I'm writing this one off to purple smoke and mirrors. Why GoogleEarth seg-faulted on the first install of the Nvidia driver, and not on the -re-install, I don't know.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.