Le lundi 07 janvier 2013, Fran�ois ANDRIOT a �crit : > Le 07/01/2013 15:12, Patrick Serru a �crit : >> Hi All, >> >> If I lauch GE from a Konsol, it gives: >> /opt/google/earth/free/google-earth: ./googleearth-bin: /lib/ld-lsb.so.3: >> bad ELF interpreter: Aucun fichier ou dossier de ce type >> >> During some previous installation tryes, I sow that the problem >> was coming from a library requested by a component of Trinity. Can >> someone tell me, please, how to do to be able to run Google Earth, while >> using TDE as windows manager? >> >> Thank you >> Patrick >> > > Hello, > it looks like you are installing a 32 bits application on a 64 bits > machine. > I guess the 32 bits library /lib/ld-lsb.so.3 is missing on your system. > > To find which package to install, just type: > yum provides /lib/ld-lsb.so.3 > > Then install the package (I guess the name: > yum install redhat-lsb.i686 > > > Francois > --------------------------------------------------------------------- Thank you Fran�ois, The resulting text of the command is attached. The tail of it being: protection contre les diff�rentes versions de biblioth�ques�: qt3-3.3.8b-41.fc17.i686 != 1:qt3-3.3.8.d-9.fc17.x86_64 The previous tryed command was "install redhat-lsb-4.1-5.fc17.i686"... Cheers Patrick
# yum install redhat-lsb.i686 Modules compl�mentaires charg�s�: langpacks, presto, refresh-packagekit Repository trinity-3.5.13 is listed more than once in the configuration Repository trinity-3.5.13-noarch is listed more than once in the configurat ion Repository trinity-3.5.13-source is listed more than once in the configurat ion google-chrome | 951 B 00:00 google-earth | 951 B 00:00 rpmfusion-free-updates | 3.3 kB 00:00 rpmfusion-nonfree-updates | 3.3 kB 00:00 trinity-3.5.13 | 2.7 kB 00:00 trinity-3.5.13-noarch | 2.6 kB 00:00 Could not retrieve mirrorlist http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/f17/trinity-3.5.13-SRPMS.list error was 12: Timeout on http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/f17/trinity-3.5.13-SRPMS.list: (28, '') trinity-3.5.13-source | 2.6 kB 00:00 trinity-extras | 2.7 kB 00:00 trinity-extras-noarch | 2.6 kB 00:00 trinity-extras-source | 2.6 kB 00:00 updates/17/x86_64/metalink | 45 kB 00:00 updates | 4.7 kB 00:00 updates/primary_db | 7.3 MB 01:06 google-chrome/primary | 1.4 kB 00:05 updates/group_gz | 439 kB 00:03 google-chrome 3/3 R�solution des d�pendances --> Lancement de la transaction de test ---> Le paquet redhat-lsb.i686 0:4.1-5.fc17 sera install� --> Traitement de la d�pendance�: redhat-lsb-desktop(x86-32) = 4.1 pour le paquet�: redhat-lsb-4.1-5.fc17.i686 --> Traitement de la d�pendance�: redhat-lsb-cxx(x86-32) = 4.1 pour le paquet�: redhat-lsb-4.1-5.fc17.i686 --> Traitement de la d�pendance�: redhat-lsb-core(x86-32) = 4.1 pour le paquet�: redhat-lsb-4.1-5.fc17.i686 --> Lancement de la transaction de test ---> Le paquet redhat-lsb-core.i686 0:4.1-5.fc17 sera install� --> Traitement de la d�pendance�: redhat-lsb-submod-security(x86-32) = 4.1 pour le paquet�: redhat-lsb-core-4.1-5.fc17.i686 --> Traitement de la d�pendance�: pam(x86-32) pour le paquet�: redhat-lsb-core-4.1-5.fc17.i686 ---> Le paquet redhat-lsb-cxx.i686 0:4.1-5.fc17 sera install� ---> Le paquet redhat-lsb-desktop.i686 0:4.1-5.fc17 sera install� --> Traitement de la d�pendance�: redhat-lsb-submod-multimedia(x86-32) = 4.1 pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: qt3(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: qt-x11(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: qt(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: libpng-compat(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: libXt(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: gtk2(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: gdk-pixbuf2(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Traitement de la d�pendance�: atk(x86-32) pour le paquet�: redhat-lsb-desktop-4.1-5.fc17.i686 --> Lancement de la transaction de test ---> Le paquet atk.i686 0:2.4.0-1.fc17 sera install� ---> Le paquet gdk-pixbuf2.i686 0:2.26.1-1.fc17 sera install� --> Traitement de la d�pendance�: libtiff.so.3 pour le paquet�: gdk-pixbuf2-2.26.1-1.fc17.i686 --> Traitement de la d�pendance�: libjasper.so.1 pour le paquet�: gdk-pixbuf2-2.26.1-1.fc17.i686 ---> Le paquet gtk2.i686 0:2.24.13-1.fc17 sera install� --> Traitement de la d�pendance�: libcups.so.2 pour le paquet�: gtk2-2.24.13-1.fc17.i686 --> Traitement de la d�pendance�: libXrandr.so.2 pour le paquet�: gtk2-2.24.13-1.fc17.i686 --> Traitement de la d�pendance�: libXinerama.so.1 pour le paquet�: gtk2-2.24.13-1.fc17.i686 --> Traitement de la d�pendance�: libXcomposite.so.1 pour le paquet�: gtk2-2.24.13-1.fc17.i686 ---> Le paquet libXt.i686 0:1.1.2-2.fc17 sera install� ---> Le paquet libpng-compat.i686 2:1.5.10-1.fc17 sera install� ---> Le paquet pam.i686 0:1.1.5-7.fc17 sera install� --> Traitement de la d�pendance�: libdb-4.8.so pour le paquet�: pam-1.1.5-7.fc17.i686 --> Traitement de la d�pendance�: libcrack.so.2 pour le paquet�: pam-1.1.5-7.fc17.i686 --> Traitement de la d�pendance�: libaudit.so.1 pour le paquet�: pam-1.1.5-7.fc17.i686 ---> Le paquet qt.i686 1:4.8.4-1.fc17 sera install� ---> Le paquet qt-x11.i686 1:4.8.4-1.fc17 sera install� --> Traitement de la d�pendance�: libmng.so.1 pour le paquet�: 1:qt-x11-4.8.4-1.fc17.i686 ---> Le paquet qt3.i686 0:3.3.8b-41.fc17 sera install� ---> Le paquet redhat-lsb-submod-multimedia.i686 0:4.1-5.fc17 sera install� ---> Le paquet redhat-lsb-submod-security.i686 0:4.1-5.fc17 sera install� --> Lancement de la transaction de test ---> Le paquet audit-libs.i686 0:2.2.1-1.fc17 sera install� ---> Le paquet cracklib.i686 0:2.8.18-3.fc17 sera install� ---> Le paquet cups-libs.i686 1:1.5.4-11.fc17 sera install� --> Traitement de la d�pendance�: libavahi-common.so.3 pour le paquet�: 1:cups-libs-1.5.4-11.fc17.i686 --> Traitement de la d�pendance�: libavahi-client.so.3 pour le paquet�: 1:cups-libs-1.5.4-11.fc17.i686 ---> Le paquet db4.i686 0:4.8.30-10.fc17 sera install� ---> Le paquet jasper-libs.i686 0:1.900.1-19.fc17 sera install� ---> Le paquet libXcomposite.i686 0:0.4.3-3.fc17 sera install� ---> Le paquet libXinerama.i686 0:1.1.2-1.fc17 sera install� ---> Le paquet libXrandr.i686 0:1.3.1-3.fc17 sera install� ---> Le paquet libmng.i686 0:1.0.10-6.fc17 sera install� ---> Le paquet libtiff.i686 0:3.9.7-1.fc17 sera install� --> Lancement de la transaction de test ---> Le paquet avahi-libs.i686 0:0.6.31-5.fc17 sera install� --> R�solution des d�pendances termin�e Erreur�: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for qt3 which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of qt3 of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude qt3.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of qt3 installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of qt3 installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). protection contre les diff�rentes versions de biblioth�ques�: qt3-3.3.8b-41.fc17.i686 != 1:qt3-3.3.8.d-9.fc17.x86_64