Google Earth

From the project web page:

Google Earth allows you to travel the world through a virtual globe and view satellite imagery, maps, terrain, 3D buildings, and much more. With Google Earth's rich, geographical content, you are able to experience a more realistic view of the world. You can fly to your favorite place, search for businesses and even navigate through directions.

Installation

Install the google-earth-proAUR package.

Troubleshooting
Tip: See the official support forum for topics not covered here.

Crash on startup

Google Earth can crash on startup for numerous reasons. Here are some of the most common ones.

Startup tips are enabled

While startup tips can be useful, they are also known to cause crashes. To disable them, change or add the line below to the ~/.config/Google/GoogleEarthPro.conf:

~/.config/Google/GoogleEarthPro.conf
[General]
enableTips=false

No new line at the end of ~/.drirc

This can cause a crash with -dri drivers:

$ echo >> ~/.drirc

Corrupt settings

In case the cache is corrupt and needs recreation, remove it:

$ rm -r ~/.googleearth/Cache/

If that did not work, try removing the whole settings directory:

$ rm -r ~/.googleearth/

Another crash happened while handling crash!

You may try removing the following:

$ rm -f ~/.googleearth/Cache/cookies ~/.googleearth/instance-running-lock

Panoramio photos not working

There have been numerous reports on this in the Google Earth forums with varying solutions.

Graphical corruption

Either refer to the #Corrupt settings section above or disable texture compression in Tools > Options... > 3D View > Compress.

Earth shows nothing but yellow borders

Taken from the changelog of 7.0.3 this issue has improved to some extent but overall it is still there:

Imagery now displays for Linux users running specific families of Intel GPUs.

Excessive memory use

Memory use can be controlled by limiting the maximum cache size in Tools > Options... > Cache, or by lowering the graphics settings in the 3D View tab.

gollark: LyricLy claims that it was obviously mine because of the formatting and use of numpy. This is wrong and ridiculous. The real reason it was obviously mine is that it does the usual gollark thing of just implementing a weird algorithm and not doing much else.
gollark: They scheduled it for 24 hours, bee.
gollark: Anyway, since LyricLy is done lyricing, it is time for me to ramble incoherently about my entry (#7±5).
gollark: Alternatively, just add a backdoor and do it later. Somehow nobody noticed me doing that in #9. Anyway, I *do* have a cool image-based esolang sitting around to use somewhere. Maybe I could incorporate that.
gollark: The obvious solution is to reveal all implementation details of lyriclysite™ so we can do that.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.