Undefined Symbol Problem

Woodsman · 03-18-2011, 09:40 AM

First, I would be grateful for some good links for troubleshooting or a good explanation what causes these infamous "undefined symbol" error messages. I would like to have a better grasp for troubleshooting these types of errors.

Here are the error messages I see:

Code:

kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OPENSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OPENSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms_conf

Starting Akregator causes the messages.

/usr/lib/libcrypto.so.0.9.8 is installed by the openssl packages. Apparently Akregator uses ssl?

This is on a 12.2 box with KDE 3.5.10.

I didn't notice these messages until recently, but I am certain I did not start receiving them until recently.

I replaced the two openssl packages with older versions, all the way back to the original packages that came with 12.2. No luck, I still saw the messages. Perhaps there is something else Akregator does that indirectly uses the ssl libraries.

Much thanks.

ponce · 03-18-2011, 09:48 AM

maybe it's because kdelibs (the warning seems to come from there) was built against an openssl that uses those symbols (and has been later upgraded) or you got a mismatch between openssl libraries and headers (found hints here).

Woodsman · 03-18-2011, 12:54 PM

I haven't solved the root problem, but I made some progress. A couple of weeks ago I added a new feed. I did not pay attention that I added an https address rather than http. I changed the address to http and the errors stopped. I can still cause the errors by changing any feed URL to https.

So the noise is somewhat less, but I still would like to know how to truly repair the problem. I might try recompiling kdelibs and kdepim against the new openssl packages, but that is pretty much a shot in the dark.

I appreciate any other ideas.

volkerdi · 03-18-2011, 01:24 PM

OpenSSL has produced those warnings for as long as I can remember.

Woodsman · 03-18-2011, 01:51 PM

Quote:

OpenSSL has produced those warnings for as long as I can remember.

Ah.

Well, another good tidbit came out of this. While browsing for ideas I came across some information about SSL2 being obsolete. I remember reading that many moons ago, but I wondered whether I had any such options still set that way that might cause the error messages. I discovered that I had SSL2 enabled. No big deal, but I cleared those settings and some stale certificates.

So the error messages likely then are unresolvable except from upstream, but the journey and thread were not a total waste.