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.12
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 .. 58 59 60 61 62 63 64 65 66 67 68 .. 106 Next › Last »

mrechte commented on 2012-11-29 09:42 (UTC)

Well, sort of: Stacktrace from glibc: ./libgoogleearth_free.so(+0x1e9cfb)[0xf75e0cfb] ./libgoogleearth_free.so(+0x1e9f43)[0xf75e0f43] linux-gate.so.1(__kernel_sigreturn+0x0)[0xf7796400]

Det commented on 2012-11-29 09:36 (UTC)

I just re-uploaded 6.2 using the Mint repositories as that's apparently the only place in the world I could find it. The tarball for the new laggy 7.0 beta is still here, in case someone insists on it: http://www29.zippyshare.com/v/24125743/file.html

Det commented on 2012-11-29 09:20 (UTC)

The _same_ one? You sure of that?

mrechte commented on 2012-11-29 07:17 (UTC)

I removed the /etc/fonts/conf.d/65-fonts-persian.conf link. Now I just get the GE splash screen followed by the same error.

TheWretched commented on 2012-11-28 17:11 (UTC)

I don't always stab myself, but when I do I do it with a need for more than 4Gb of ram.

Det commented on 2012-11-28 17:08 (UTC)

Stab yourself inside it? That would be quite a trick. But thanks for the suggestion. I might just try these out one day.

TheWretched commented on 2012-11-28 17:03 (UTC)

I thought it was a shame sharpfonts is down, so here's the sharpfonts files in the interim. http://support.mcsnet.ca/sharpfonts/sharpfonts.tar In case anyone want's to try what I mentioned below.

TheWretched commented on 2012-11-28 16:55 (UTC)

For what it's worth. I was just loading a new system and came across this package and it's problems. It seems to be working fine for me (knock on wood) with my typical setup and I thought I would mention it just for the sake of it, in case it helps anyone. I am using KDE and the latest nvidia proprietary drivers 8xxx series hardware. My font configuration is set up in the way that I install the Windows 7 fonts, and use the sharpfonts.co.cc fontconfig files. Since sharpfonts.co.cc is down, and the aur package for sharpfonts also doesn't work because of this it's a bit of a pickle, I had them saved on my ftp however. I modified the ms rules.conf to one I saw linked in the aur sharpfonts package as well, and placed them all under the /etc/fonts/conf.d/ folder as 99-foo.conf. I don't really know if using the MS fonts with rules has anything to do with it running seemingly quite well. But it does work and is the only way I have ever been able to get fonts that don't look like they make me want to stab myself in 64 bit arch.

Det commented on 2012-11-28 15:22 (UTC)

You've motherf*cking got to be kidding me. For f*ck's sake [...]. E: Ok, credit where it's due, the fontconfig package was updated just the other day in addition to neither of the edit hacks described here actually working anymore. So it's either: 1) Remove _all_ the <alias> tags from under "<!-- Name changes and spelling variant aliases -->" OR 2) Remove the symlink "/etc/fonts/conf.d/65-fonts-persian.conf" -> "/etc/fonts/conf.avail/65-fonts-persian.conf" (or just the file being pointed to itself). I'm too lazy and still so delightfully and yet quite so stilishly, while at the same time piteously pissed off about this to go through any more edit hack searches.. at this point.