stack trace on startup on linux, how to drill down to find the culprit

[David Shrader]

Hello,

When I try to start spyder on a RedHat 7.9-based linux machine, I get a stack trace after several seconds. I've gone through the troubleshooting helps on https://docs.spyder-ide.org, and have found that `python start.py` generates the same stack trace:

$> python start.py
link image0 hasn't been detected!
[30716:30716:0217/160737.050658:FATAL:zygote_host_impl_linux.cc(165)] Check failed: process.IsValid(). Failed to launch zygote process
#0 0x2b55d04fe0be <unknown>
#1 0x2b55d05106c2 <unknown>
#2 0x2b55d027a8f8 <unknown>
#3 0x2b55d0279b07 <unknown>
#4 0x2b55d0279e96 <unknown>
#5 0x2b55d00249a1 <unknown>
#6 0x2b55d0028727 <unknown>
#7 0x2b55cfeba542 <unknown>
#8 0x2b55cfeba718 <unknown>
#9 0x2b55cfeb1681 <unknown>
#10 0x2b55cfeb1732 QtWebEngineCore::WebContentsAdapter::WebContentsAdapter()
#11 0x2b55cf721376 <unknown>
#12 0x2b55cf71f0c4 <unknown>
#13 0x2b55cf71f252 QWebEnginePage::QWebEnginePage()
#14 0x2b55cf6d9689 sipQWebEnginePage::sipQWebEnginePage()
#15 0x2b55cf6d9812 init_type_QWebEnginePage
#16 0x2b55ce3f98e4 <unknown>
#17 0x559cf3b509bb _PyObject_MakeTpCall
#18 0x559cf3bd68b4 _PyEval_EvalFrameDefault
#19 0x559cf3b8eb0d _PyEval_EvalCode
#20 0x559cf3b8f527 _PyFunction_Vectorcall
#21 0x559cf3b8084e _PyObject_FastCallDictTstate
#22 0x559cf3b8a3d9 slot_tp_init
#23 0x559cf3b509bb _PyObject_MakeTpCall
#24 0x559cf3bd7853 _PyEval_EvalFrameDefault
#25 0x559cf3b8eb0d _PyEval_EvalCode
#26 0x559cf3b8f527 _PyFunction_Vectorcall
#27 0x559cf3b807ca _PyObject_FastCallDictTstate
#28 0x559cf3b8a3d9 slot_tp_init
#29 0x559cf3b509bb _PyObject_MakeTpCall
#30 0x559cf3bd68b4 _PyEval_EvalFrameDefault
#31 0x559cf3b8eb0d _PyEval_EvalCode
#32 0x559cf3b8f527 _PyFunction_Vectorcall
#33 0x559cf3b807ca _PyObject_FastCallDictTstate
#34 0x559cf3b8a3d9 slot_tp_init
#35 0x559cf3b509bb _PyObject_MakeTpCall
#36 0x559cf3bd68b4 _PyEval_EvalFrameDefault
#37 0x559cf3b8eb0d _PyEval_EvalCode
#38 0x559cf3b8f527 _PyFunction_Vectorcall
#39 0x559cf3b8084e _PyObject_FastCallDictTstate
#40 0x559cf3b8a3d9 slot_tp_init
#41 0x559cf3b509bb _PyObject_MakeTpCall
#42 0x559cf3bd7853 _PyEval_EvalFrameDefault
#43 0x559cf3bbb9b3 method_vectorcall
#44 0x559cf3b0690b _PyEval_EvalFrameDefault.cold.2975
#45 0x559cf3b8eb0d _PyEval_EvalCode
#46 0x559cf3b8f527 _PyFunction_Vectorcall
#47 0x559cf3b8084e _PyObject_FastCallDictTstate
#48 0x559cf3b8a3d9 slot_tp_init
#49 0x559cf3b509bb _PyObject_MakeTpCall
#50 0x559cf3bd7853 _PyEval_EvalFrameDefault
#51 0x559cf3bbb9b3 method_vectorcall
#52 0x559cf3b05fdc _PyEval_EvalFrameDefault.cold.2975
#53 0x559cf3bbb9b3 method_vectorcall
#54 0x559cf3b0690b _PyEval_EvalFrameDefault.cold.2975
#55 0x559cf3bbb9b3 method_vectorcall
#56 0x559cf3b05fdc _PyEval_EvalFrameDefault.cold.2975
#57 0x559cf3b8f753 _PyFunction_Vectorcall
#58 0x559cf3b06ebb _PyEval_EvalFrameDefault.cold.2975
#59 0x559cf3b8f753 _PyFunction_Vectorcall
#60 0x559cf3b05fdc _PyEval_EvalFrameDefault.cold.2975
#61 0x559cf3b8f753 _PyFunction_Vectorcall

Aborted

This build of spyder was done through Anaconda Python 2021.11 (python 3.9, spyder 5.1.5) on RedHat 7.9 Linux. I have created a conda environment and have installed the latest spyder available to conda (5.1.5) and the myriad of dependencies, and I get the same stack trace. The same installation works on a SUSE 15 SP2 machine, so I am pretty sure the problem lies somewhere in the system files that get pulled in. I'm just not able to tell from the stack trace where the problem lies. Does anyone have any tips or tricks on drilling down on this so that I can try to find the offending library?

Thanks for any and all help!