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: 1082
Popularity: 2.22
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 .. 68 69 70 71 72 73 74 75 76 77 78 .. 106 Next › Last »

giddie commented on 2012-04-07 22:43 (UTC)

@akspecs Thanks for the info. Yeah, it's clearly a driver issue. I think there's still some room for improvement for SandyBridge support, to be honest, although it's *so* much better than a year ago. I have the same issue if I try to "Experience MapsGL" in Google Maps. I get a few seconds of 3D, and then a lockup, although when that happened I did get some crippled activity following that, but it was pretty clear that 3D acceleration had gone out the window.

akspecs commented on 2012-04-07 22:22 (UTC)

@giddle I run on HD3000 graphics as well and have similar behavior as do you. If running Gnome, it can handle the crash by killing X, but then when restarting X it will restart in fallback mode. On a lower end system, running i686 nvidia nvs quadro 135m graphics it runs fine. So it my have to do with xf86-video-intel or lib32-intel-dri or something :/

Det commented on 2012-04-07 19:34 (UTC)

Not gonna help you two but out of curiosity I tested which browsers asked whether to resend the data. It turns out both Firefox and Chrome have started doing this since their first public releases (0.8 and 0.2.149.27 Beta, respectively). IE also does this at least since 7 (nothing lower works with Windows 7), while Opera doesn't with neither the latest 12.00 alpha (1351) or the stable 11.62.

giddie commented on 2012-04-07 15:32 (UTC)

Any idea why I get a complete system freeze after a minute or so when using Google Earth with HD3000 Intel graphics?

akspecs commented on 2012-04-07 12:10 (UTC)

I still get crash signal 11 after installing lib32-intel-dri - just 30 seconds after I start rather than immediately after startup.

<deleted-account> commented on 2012-04-07 11:19 (UTC)

T'was an error 40. :-( My browser is Firefox 11.0

Det commented on 2012-04-06 20:39 (UTC)

Upgrade to a better browser then. Modern firefox and chrome versions both ask first whether to resend the same thing.

dgbaley27 commented on 2012-04-06 20:33 (UTC)

Det: He posted, then hit refresh awaiting your reply and the browser resent the data.

Det commented on 2012-04-06 18:19 (UTC)

Because there was no new release in between. BTW. How come did you post the same thing twice?

<deleted-account> commented on 2012-04-06 17:42 (UTC)

I did. The file ~/dridc did not exist. After the echo command I had an empty file, but that didn't prevent google-earth from segfaulting. I have the package 'nouveau-dri' installed. BTW. How come the PKBUILD was updated without a version number increase?