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: 1076
Popularity: 3.44
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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 105 Next › Last »

Det commented on 2018-01-24 22:27 (UTC) (edited on 2018-01-24 22:56 (UTC) by Det)

This might be affecting some people....: https://wiki.archlinux.org/index.php/Locale#My_system_is_still_using_wrong_language

Just try: $ LANG=C google-earth-pro

Det commented on 2018-01-24 22:06 (UTC)

Is this issue really this inconsistent that overriding LANG works for some (like me), and LC_NUMERIC for others?

dviktor commented on 2018-01-24 21:36 (UTC)

May be it worth to include LC_NUMERIC fix to the PKGBUILD?

Nano commented on 2018-01-15 18:04 (UTC)

Ok, I add en_US.UTF-8 variable in locales, run locale-gen and change the line at the end of googleearth file but nothing, do not work.

Nano commented on 2018-01-15 17:53 (UTC)

No, I am Spanish.

Why?

Det commented on 2018-01-15 17:40 (UTC)

You even have en_US.UTF-8 available in locales?

Nano commented on 2018-01-15 17:39 (UTC)

Ok, thanks anyway.

Does anyone have a solution?

abouvier commented on 2018-01-12 02:11 (UTC)

No, it's working for me, so I don't know :p

Nano commented on 2018-01-11 22:00 (UTC)

Hey! Thanks Doskoi, I forgot this matter until today.

I remplace this line but do not work.

The problem persist.

Have you got another idea?

Det commented on 2017-12-05 16:17 (UTC)

Good question.