Article 5HCW4 Google Earth Segfaults

Google Earth Segfaults

by
business_kid
from LinuxQuestions.org on (#5HCW4)
I'm on the Slack64-Current iso of 2021-04-20, and stuck in the latest GE (version 7.3) because the previous one (about 10 months back) was segfaulting. I got the .deb, ran deb2targz, exploded that, and made a package; then I installed it.

Here's their script, named as googleearth & google-earth-pro Code:#!/bin/bash
# This script configures any environment prerequisites needed by Google Earth.
# Start Google Earth using this script rather than googleearth-bin directly.

# If you want to use an external copy of GPSBabel, you can specify it here.
# if [[ -z "$GPSBABEL" ]]; then export GPSBABEL="$(which gpsbabel)"; fi

# If DISPLAY is not set, try to autodetect a value.
if [[ -z "$DISPLAY" ]]; then
echo "WARNING: DISPLAY environment variable is not set."
x_displays=(/tmp/.X11-unix/X*)
display="${x_displays[0]}"
if [[ -e "$display" ]]; then
export DISPLAY=":${display/*X/}"
echo " Found ${display}; setting DISPLAY=\"${DISPLAY}\"."
else
echo " X11 display not detected; Google Earth may not run correctly."
fi
fi

"$(dirname "$(readlink -f "$0")")/googleearth-bin" "$@" and that last line always, always hangs.
Code:bash-5.1$ google-earth-pro
/usr/bin/google-earth-pro: line 21: 13728 Segmentation fault "$(dirname "$(readlink -f "$0")")/googleearth-bin" "$@"

bash-5.1$ ./googleearth
./googleearth: line 21: 13745 Segmentation fault "$(dirname "$(readlink -f "$0")")/googleearth-bin" "$@"

./googleearth-bin
Segmentation faultThis time the binary does too. Nothing applicable showed in web searches except that Ubuntu-21.04 managed to screw up curl somehow. Any thoughts?latest?d=yIl2AUoC8zA latest?i=ElfEBSnN9D8:QiWQQn15DEk:F7zBnMy latest?i=ElfEBSnN9D8:QiWQQn15DEk:V_sGLiP latest?d=qj6IDK7rITs latest?i=ElfEBSnN9D8:QiWQQn15DEk:gIN9vFwElfEBSnN9D8
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments