[opensuse-factory] Kodi/openssl/python segfault on TW
Kodi on my TW system has suddenly started to crash after showing the main screen on startup. The cause is a segfault in libcrypto.so. Top of the stack trace: #0 0x00007fffee2cf2e5 in OPENSSL_ia32_cpuid () from /lib64/libcrypto.so.1.0.0 #1 0x00007fff288e2943 in ?? () from /usr/lib64/libcrypto.so.38 #2 0x00007fff288c4c17 in _init () from /usr/lib64/libcrypto.so.38 #3 0x00007fff2888aaf0 in ?? () from /usr/lib64/libcrypto.so.38 #4 0x00007ffff7de83ba in call_init.part () from /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7de850b in _dl_init () from /lib64/ld-linux-x86-64.so.2 #6 0x00007ffff7dec9b8 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #7 0x00007fffef0d1924 in _dl_catch_error () from /lib64/libc.so.6 #8 0x00007ffff7dec159 in _dl_open () from /lib64/ld-linux-x86-64.so.2 #9 0x00007ffff5eb4ff6 in dlopen_doit () from /lib64/libdl.so.2 #10 0x00007fffef0d1924 in _dl_catch_error () from /lib64/libc.so.6 #11 0x00007ffff5eb56d9 in _dlerror_run () from /lib64/libdl.so.2 #12 0x00007ffff5eb5092 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2 #13 0x00007fff29943321 in ?? () from /usr/lib64/python2.7/lib-dynload/_ctypes.so #14 0x00007ffff61ca771 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #15 0x00007ffff61c9884 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #16 0x00007ffff61779ee in ?? () from /usr/lib64/libpython2.7.so.1.0 #17 0x00007ffff6160723 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 The kodi crash log shows no useful info whatsoever. I don't remember any recent updates to kodi or openssl, so I'm puzzled. Any suggestions? Thanks Albert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2017-04-25 17:41, Albert Koelmans wrote:
Right, so how did kodi manage to load both libressl and openssl into the same process image? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Is libressl the one with version number 38? On 25/04/17 17:19, Jan Engelhardt wrote:
Right, so how did kodi manage to load both libressl and openssl into the same process image?
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2017-04-25 18:46, Albert Koelmans wrote:
libressl 2.5.0 consists of libcrypto38, libssl39 and libtls11. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
For some reason, libcrypto38 had been installed together with openssl. After cleanup things are working normally now. Many thanks for the help. Albert On 25/04/17 21:54, Jan Engelhardt wrote:
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-04-26 08:30, Albert Koelmans wrote:
For some reason, libcrypto38 had been installed together with openssl. After cleanup things are working normally now.
They both can be installed concurrently; but one will have to check why both got loaded. That would hint towards kodi/python doing an unwanted dlopen(libcrypto.so) at some point and failure to use the libcrypto linked at build time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2017-04-25 17:41, Albert Koelmans wrote:
Right, so how did kodi manage to load both libressl and openssl into the same process image? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Is libressl the one with version number 38? On 25/04/17 17:19, Jan Engelhardt wrote:
Right, so how did kodi manage to load both libressl and openssl into the same process image?
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2017-04-25 18:46, Albert Koelmans wrote:
libressl 2.5.0 consists of libcrypto38, libssl39 and libtls11. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
For some reason, libcrypto38 had been installed together with openssl. After cleanup things are working normally now. Many thanks for the help. Albert On 25/04/17 21:54, Jan Engelhardt wrote:
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-04-26 08:30, Albert Koelmans wrote:
For some reason, libcrypto38 had been installed together with openssl. After cleanup things are working normally now.
They both can be installed concurrently; but one will have to check why both got loaded. That would hint towards kodi/python doing an unwanted dlopen(libcrypto.so) at some point and failure to use the libcrypto linked at build time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Albert Koelmans -
Jan Engelhardt