Package Details: google-earth-pro 7.3.6.10201-2

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: LicenseRef-Google-custom
Provides: google-earth
Submitter: Det
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 1081
Popularity: 2.55
First Submitted: 2017-01-23 16:08 (UTC)
Last Updated: 2025-05-06 10:32 (UTC)

Pinned Comments

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 .. 47 48 49 50 51 52 53 54 55 56 57 .. 106 Next › Last »

lineage commented on 2013-02-04 13:40 (UTC)

Hi Det, No, I didn't have time to download and build a GE6 pkg this morning. Will try to do it later. Thanks for the paste. I wondered if the 32 [i686 ;-)] vs 64 bit would make any difference.

kolombo commented on 2013-02-04 11:29 (UTC)

I have fixed my crush installing https://launchpadlibrarian.net/7037027/libGL.so.1. But earth view is completelly grey :)

Det commented on 2013-02-04 11:25 (UTC)

Yes, I have an x86 machine, but my system is 64-bit, if that's what you meant :). Not that it matters, since the app is 32-bit anyway. I had a look at it yesterday when I compared the two and I can't say it helps (the one with 65-fonts-persian.conf): http://pastebin.com/B7FwBbxV The hyphen/hash break at line 861 signals the differences after the 3rd gettimeofday() (which in my case is called twice in a row). E: You had a look at the GE6 log yet?

lineage commented on 2013-02-04 09:06 (UTC)

Det, libGL didn't help. Two more datapoints. Google earth doesn't even get as far as creating a crashlog. If I run onto a remote X display on another machine I get the same behavior. If I run the googleearth (6.2) from the remote machine with its display on this machine, it does a lot better, we get spash screen and eventually a crashlog. If you have this v7 installed on an x86 machine, can you tell me what happens on your system after the futex call? Might be a useful clue.

lineage commented on 2013-02-04 08:45 (UTC)

Thanks Det, I'll try the libGL. The X driver for the graphics on this CPU has caused me obscure problems before. If all else fails I'll try v6 too, but I have a bad feeling it won't help.

Det commented on 2013-02-04 00:05 (UTC)

No, it has nothing at all to do with /etc/localtime. There's also the business interest with Windows and keeping your source closed. That's why other people can't fix the black screen problems (which are Intel/Mesa related anyway).

olive commented on 2013-02-03 22:46 (UTC)

Just my thought. How does Google manage to make a so buggy software? It crashes because we have a cyrillic font, it does not show the earth just black instead, and now /etc/localtime??? We could expect more from Google

Det commented on 2013-02-03 22:27 (UTC)

Yeah, that's a really obscure error (posting in here for everyone to see: http://pastebin.com/jgEYLStx) and I'm afraid I've got nothing to go on. You could try installing https://launchpadlibrarian.net/7037027/libGL.so.1 to /opt/google/earth/free/ and see if it makes a difference (an old workaround for Intel cards). But I doubt it will.

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 106 Next › Last »