Package Details: google-earth-pro 7.3.6.9796-1

Git Clone URL: https://aur.archlinux.org/google-earth-pro.git (read-only, click to copy)
Package Base: google-earth-pro
Description: 3D interface to explore the globe, terrain, streets, buildings and other planets (Pro version)
Upstream URL: https://www.google.com/earth/
Licenses: custom
Provides: google-earth
Submitter: Det
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 1077
Popularity: 0.64
First Submitted: 2017-01-23 16:08 (UTC)
Last Updated: 2024-02-27 14:45 (UTC)

Pinned Comments

iyanmv commented on 2022-12-13 22:54 (UTC)

I will not update (for now) to the latest version 7.3.6.9326 because it crashes continuously for me.

stronnag commented on 2022-06-18 17:03 (UTC)

Thanks, unfortunate timing then.

For reference, with Gnome shell / wayland I need to

unset QT_QPA_PLATFORMTHEME
unset QT_QPA_PLATFORM

to avoid

Google Earth has caught signal 6.

Det commented on 2017-08-24 15:33 (UTC) (edited on 2017-12-05 16:17 (UTC) by Det)

✔ NOTE The "Free" Google Earth has been dropped: https://support.google.com/earth/answer/168344?hl=en

All future updates go to Google Earth Pro (also free): https://aur.archlinux.org/packages/google-earth-pro/

Latest Comments

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 105 Next › Last »

dront78 commented on 2012-09-08 18:46 (UTC)

Have anyone tryed http://swyear.blogspot.com/2011/05/run-google-earth-6-on-opensuse.html to fix antialiasing?

Det commented on 2012-08-28 13:37 (UTC)

It's in [multilib]: https://wiki.archlinux.org/index.php/Multilib

smu commented on 2012-08-28 07:38 (UTC)

# packer -S google-earth Dependency `lib32-fontconfig' of `google-earth' does not exist.

Det commented on 2012-08-26 11:42 (UTC)

Glad we got that figured out.

DevRandom commented on 2012-08-26 02:09 (UTC)

To people who still have trouble with: ./googleearth: line 43: ./googleearth-bin: No such file or directory You are missing /lib/ld-lsb.so.3, which is a symlink installed by ld-lsb. Check the following: - Multilib repo active in pacman.conf - lib32-glibc installed The recent switch from /lib to a symlink blew up both lib32-glibc and ld-lsb on my setup, and I had accidentally deactivated the multilib repository in pacman.conf before updating the packages. This led to exactly this error.

Det commented on 2012-08-19 18:36 (UTC)

That's something you raarely hear from a fellow user. You are welcome.

jhernberg commented on 2012-08-19 16:13 (UTC)

You are right it doesn't render correctly when adding that lib. Can't seem to find another way of making it work. So I guess it's pacman -R time :) Thanks for your time and best of luck with the package though!

Det commented on 2012-08-19 15:20 (UTC)

Some people say removing or adding a new line to .drirc helps (also mentioned in the post install/upgrade). Then there's other discoveries in different sites as well, including disabling the Start-Up Tips: http://www.webupd8.org/2010/10/fix-google-earth-crashing-on-startup-in.html You're not alone. For some people replacing intel-dri with the launchpad libGL helps, for some it's the othe way around. I've just heard that using the launchpad libGL there's some flickering and/or missing polygons. You could try cycling through these to see, if it's of any assistance: http://productforums.google.com/forum/#!searchin/earth/signal$2011

jhernberg commented on 2012-08-19 15:02 (UTC)

FWIW, it crashes with a "Google Earth has caught signal 11." until I install http://librarian.launchpad.net/7037027/libGL.so.1 into /opt/google/earth/free. i686 system with intel-dri 8.0.4-2.

jhernberg commented on 2012-08-19 13:42 (UTC)

Fwiw, license.html looks ok when opened in a browser. Indeed I am getting served by another google server: Connecting to earth.google.com|74.125.230.232|:80... connected. Hopefully I am not getting my DNS spoofed :) Am online via umts dialup in Spain (telefonica). For me personally not a big problem, but I thought I'd let you know that there is a potential problem with the script. Repeating the process in /tmp yields the same result and the same checksum. Running the script on a machine in Lxembourg, yields the expected checksum of '7363c6144ebb298b1d7aec713ca8a82a'.