I’m going to be quite straightforward. Google’s not going to publish a new version to keep openSUSE users happy. Google’s requirements for Linux are on this page. When you manage to convince Ubuntu or Fedora to use curl and yast by default, then you’ll have a case.
The problem, as Google sees it, is that every Linux programmer on earth seems to have a need to publish a version of Linux that isn’t fully compatible with anyone else’s. Especially rolling releases.
As I see it, this is one of the reasons Linux can’t produce a user friendly, popular desktop version. The Linux world needs to have a constitutional convention and ask Linus to create some system that makes sense before he gets any older and crankier
The issue is caused by a newer version of curl. Any idea how to work around?
All I had to do is create a dummy file with touch /opt/google/earth/pro
/libcurl.so.4 and it then ran fine. Its quite odd really as creating a symlink to the actual library is /lib64 didn’t work, but it must be falling back to using it anyway.
curl 7.77.0 is available in my distro’s repo now. I ran Google Earth version 7.3.3.7721 immediately after updating and it ran correctly without any segmentation faults.
Out of curiosity I installed GE (7.3.4.8248) on TW VM (20210723) GNOME/Wayland (ignoring mesa-libGLU dependency) and it seems to run - at least, it starts and actually searches and displays places.
Hi
Likewise, on real hardware and GNOME DE with Xorg, there was the curl issue awhile back but that seems to be resolved now… tested 7.3.4 with AMD and Nvidia.
Yesterday’s download from link on https://support.google.com/earth/answer/21955 yielded version google-earth-pro-stable 7.3.3.7786-0. Removing this version, downloading and installing again now yielded 7.3.4.8248-0 which no longer dumps core. Apparently the Diamond Product Experts are trying to make everybody happy and replaced their blunder by a working version.