Bug 949 - Google Earth can't be installed and run.
Summary: Google Earth can't be installed and run.
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-23 03:27 CEST by Jiang Yike
Modified: 2011-04-23 19:52 CEST (History)
0 users

See Also:
Source RPM: Google Earth
CVE:
Status comment:


Attachments

Description Jiang Yike 2011-04-23 03:27:09 CEST
Description of problem:

The package google-earth-stable_current_x86_64.rpm can be installed, but can't run. When trying to run it, the error message is:

/usr/bin/google-earth: Line43: ./googleearth-bin: No such file or directory


The bin installer (GoogleEarthLinux.bin) of Google Earth 5.2 can't be installed.

When trying "sh GoogleEarthLinux.bin", the error message is:

Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 5.2.1.1588..............................................................
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
./setup.sh: Line 158: **** segment error "$setup" "$@"

When trying "./GoogleEarthLinux.bin", the error message is:

Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 5.2.1.1588..............................................................
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
./setup.sh: Line 158: **** segment error "$setup" "$@"


The number "****" is changed every time when try the two methods.

In Mandriva Linux, both of bin and rpm installers can be installed properly.
Comment 1 Ahmad Samir 2011-04-23 19:52:05 CEST
Nothing we can do about google-earth, it's a 3rd party app/installer. (You should report it to google).

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.