I have installed CS15.1 on my ubuntu and getting this error "svn: relocation error: /usr/lib/i386-linux-gnu/libserf-1.so.1: symbol GENERAL_NAME_free, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference "

[David E. Fox]

Binary package hint: libssl0.9.8

Recently, I've been getting this error whenever I try to do an svn up or run programs that depend on libssl (such as stellarium)

stellarium: relocation error: /usr/lib/libssl.so.0.9.8: symbol AVP_aes_192_cbc, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link timereference

The same error output is shown on terminal whenever I try and run an svn up to update stellarium.

Recently the system deleted libssl-dev as being unused; however, if I do a wajig whichpkg on the libssl and libcrypto files in /usr/lib/, ownership of them is claimed by libssl-dev. Figuring something was amiss, I tried reinstalling libssl-dev a few days ago, but that didn't solfe the problem.

dfox@newbox:~/stellarium$ aptitude search libssl
i A libssl-dev - SSL development libraries, header files and documentation
p libssl-ocaml - OCaml bindings for OpenSSL
p libssl-ocaml-dev - OCaml bindings for OpenSSL
i libssl0.9.8 - SSL shared libraries
p libssl0.9.8-dbg - Symbol tables for libssl and libcrypto
dfox@newbox:~/stellarium$

vn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
dfox@newbox:~/stellarium$ svn cleanup
dfox@newbox:~/stellarium$ svn up
svn: relocation error: /usr/lib/libssl.so.0.9.8: symbol AVP_aes_192_cbc, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference
dfox@newbox:~/stellarium$

Running Hardy Heron 8.04.1 fully updated, amd64 system.

[Gonzhauser (gonzhauser)]

Hits me too with Google Earth 5.

[reto.koenig (reto-koenig)]

Can confirm the same for me with Google Earth 5
Linux matrix 2.6.27-11-server #1 SMP Thu Jan 29 20:13:12 UTC 2009 x86_64 GNU/Linux fully updated

[Gonzhauser (gonzhauser)]

I have a fix:

1. Download libssl: apt-get source libssl0.9.8
2. Compile it: cd <to packge>; ./config shared; make
3. Move package to the right place: cd /usr/lib/i686/cmov; mv libssl.0.9.8 libssl.0.9.8.orig, cp <package>/libssl.so.0.9.8 /usr/lib/i686/cmov

Google Earth works for me now.

[Gonzhauser (gonzhauser)]

Of course, copying libssl.so.0.9.8 to you Google Earth directory (~/lib/google-earth in my case) works, too.

[Nicolás Lichtmaier (niqueco)]

My simple Google Earth fix was just to delete libcrypto* from its directory and let it pick up the system one.

[steliosd (dritsas)]

Nicolas, you Sir, are a genius. Renaming libcrypto.so.0.9.8 to libcrypto.so.0.9.8.bak in my google-earth directory solved it! Magique... cheers. S.

[Jim Roper (jjroper)]

Unfortunately, this ALMOST works for me. I now have GE5 up and running, with some problems.

1. Fonts on the map. Some letters do not appear, instead there is a blur where they should be. For example, a, s, u among others.

2. When I zoom closer to the surface of the earth, the image gets whiter and whiter, until, at the height I would like to be, the earch is completely whited out.

Anybody have a suggestion? I already tried other fonts, and messed with resolution and did the libss* and the libcrypto* things.

Thanks,

Jim

[David E. Fox (dfox94085)]

On Wed, Apr 1, 2009 at 7:24 AM, Jim Roper <email address hidden> wrote:
> Unfortunately, this ALMOST works for me.  I now have GE5 up and running,
> with some problems.
>
> 1.  Fonts on the map. Some letters do not appear, instead there is a
> blur where they should be.  For example, a, s, u among others.

What video card/driver are you using?

I've noticed missing letters in fonts before that are rendered in
OpenGL using the revision of the intel video driver that is in
Intrepid. Most noticeable was an application called Stellarium; much
of the letters in the text display were missing. GE had other problems
that made it unusable, most notably flickering.

I've since switched to Jaunty, and the video drivers have improved to
the point where the flickering and font abnormalities are no longer
present.

--
thanks for letting me change the magnetic patterns on your hard disk.

[Jana (jana-pursley)]

Hi all,
I moved libcrypto.so.0.9.8 to libcrypto.so.0.9.8.bak and I copied the libssl.so.0.9.8 into my google-earth dir - yet I still get this crash message about 5 seconds after typing googleearth on the promt:

"We apologize for the inconvenience, but Google Earth has crashed.
 This is a bug in the program, and should never happen under normal
 circumstances" .. etc

The begining of the crashlog has this in it:
"CRASHLOGVER 1
CRASHLOGID 0xFDD16872
APPVERMAJOR 5
APPVERMINOR 0
APPVERBUILD 11337
APPBUILDDATE Jan 28 2009
APPBUILDTIME 15:42:23
OSTYPE 11
OSVERMAJOR 2
OSVERMINOR 6
OSVERBUILD 27
OSVERPATCH 0
PID 6106
CRASHSIGNAL 11
CRASHTIME 1239379792
PROGRAMUPTIME 3"

has anyone seen this before? I'm using UBUNTU 8.10.
thanks

[Jim Roper (jjroper)]

Hi All,

I updated to Jaunty and Google Earth then works just fine.

Jim

Jana wrote on 10-Apr-09 12:17:
> Hi all,
> I moved libcrypto.so.0.9.8 to libcrypto.so.0.9.8.bak and I copied the libssl.so.0.9.8 into my google-earth dir - yet I still get this crash message about 5 seconds after typing googleearth on the promt:
>
> "We apologize for the inconvenience, but Google Earth has crashed.
> This is a bug in the program, and should never happen under normal
> circumstances" .. etc
>
> The begining of the crashlog has this in it:
> "CRASHLOGVER 1
> CRASHLOGID 0xFDD16872
> APPVERMAJOR 5
> APPVERMINOR 0
> APPVERBUILD 11337
> APPBUILDDATE Jan 28 2009
> APPBUILDTIME 15:42:23
> OSTYPE 11
> OSVERMAJOR 2
> OSVERMINOR 6
> OSVERBUILD 27
> OSVERPATCH 0
> PID 6106
> CRASHSIGNAL 11
> CRASHTIME 1239379792
> PROGRAMUPTIME 3"
>
> has anyone seen this before? I'm using UBUNTU 8.10.
> thanks
>
>

--

------------------------------------------------------------------------
James J. Roper
Smithsonian Tropical Research Institute
Bocas del Toro Marine Research Station
MRC 0580-03
Unit 9100, Box 0948
DPO AA 34002-9998

Skype-in (USA):[phone]
Skype-in (Brazil): 41 39415715

E-mail - personal: <email address hidden>
E-mail - consulting: <email address hidden>
STRI Bocas del Toro
<http://www.stri.org/english/research/facilities/marine/bocas_del_toro/index.php>
Programa de Pós-graduação em Ecologia e Conservação
<http://www.bio.ufpr.br/ecologia/>
Educational Pages <http://jjroper.googlepages.com/>
Ars Artium Consulting <http://arsartium.googlepages.com/>
9^o 21.122' N, and 82^o 15.390' W
In Google Earth, copy and paste -> 9 21.122' N, 82 15.390' W
------------------------------------------------------------------------

[sondra york (ysondra75)]

whenever i install google earth linux binary, and i go to start the program, it will open for a breif two seconds, and then it will crash again. after reading the help file for troubleshooting, i search the folder for libcrypto.so.0.9.8 and i can not find it. but i know it installed the program correctly though because after installing it says it's complete and congradulations, you have installed google earth on this machine. or something along the lines. im wondering if that's why it wont run is because there IS NO libcrypto.so.0.9.8 file. thanks and i'll appreciate any kind of help i can get. thanks again
sondra

[Maarten Bezemer (veger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 257464 and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for openssl (Ubuntu) because there has been no activity for 60 days.]

[Seth Arnold (seth-arnold)]

Swapnil, this bug has been closed for four years. If you have a problem please file a new bug.

Thanks