[SOLVED] First major oops with Plasma5 - Google Earth Pro now segfaults

bassmadrigal · 12-16-2020, 12:56 PM

Quote:

Originally Posted by LuckyCyborg

Then WHY, this thread title accuse Plasma5 when it is just an packaging issue of Google binary at best?

They weren't sure what the cause was, and they noticed the issue when Plasma5 was merged. Now that some digging has occurred, it found the issue was not tied to Plasma5, but another component of Slackware that was updated.

It was an honest mistake and something that happens semi-frequently on this forum.

rinaldij · 12-17-2020, 11:51 AM

Quote:

Originally Posted by Paulo2

Another candidate, libcrypto.so.1.0.0 shipped with Google Earth.

I downloaded an old version (7.3.0) just to see if it would run, and it did.
That version doesn't have libcrypto, so I deleted it from the ponce's SBoGit
installation and Google Earth now runs ok.

Yes:
sudo mv /opt/google/earth/pro/libcrypto.so.1.0.0 /opt/google/earth/pro/libcrypto.so.1.0.0-bak
did the job.

gmgf · 12-17-2020, 12:00 PM

Quote:

Originally Posted by LuckyCyborg

So, it wasn't the Plasma5's fault, but the CURL in -current is just too modern for the binary proprietary software shipped by Google?

Then WHY, this thread title accuse Plasma5 when it is just an packaging issue of Google binary at best?

After all, who cares about Google Earth Pro can package and ship particular libraries with it...

Because, when something goes wrong, it's plasma's fault, it's well known