Gajim constantly randomly segfaults if libgssdp is installed
Pretty much all versions of gajim always segfaulted (and continue as of 1.3.1) randomly while staying idle in desktop's systray. dmesg
says:
gajim[16572]: segfault at 560e51f609d1 ip 00007fb34cbb8d95 sp 00007fffca1c5e98 error 4 in libgobject-2.0.so.0.6600.7[7fb34cb92000+2f000]
journalctl -b0 -e --user
says:
Mar 11 00:59:47 systemd-coredump[3085]: Process 16572 (gajim) of user 1000 dumped core.
Stack trace of thread 16572:
#0 0x00007fb34cbb8d95 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x35d95)
#1 0x00007fb34cb9d265 g_object_unref (libgobject-2.0.so.0 + 0x1a265)
#2 0x00007fb337a8a0ad n/a (libgssdp-1.2.so.0 + 0xd0ad)
#3 0x00007fb337a8a923 n/a (libgssdp-1.2.so.0 + 0xd923)
#4 0x00007fb34c991ab7 n/a (libgio-2.0.so.0 + 0xa5ab7)
#5 0x00007fb34cc31f57 g_main_context_dispatch (libglib-2.0.so.0 + 0x54f57)
#6 0x00007fb34cc322d8 n/a (libglib-2.0.so.0 + 0x552d8)
#7 0x00007fb34cc3238f g_main_context_iteration (libglib-2.0.so.0 + 0x5538f)
#8 0x00007fb34c9d06a5 g_application_run (libgio-2.0.so.0 + 0xe46a5)
#9 0x00007fb34d13e42d n/a (libffi.so.8 + 0x742d)
#10 0x00007fb34d13a4f9 n/a (libffi.so.8 + 0x34f9)
#11 0x00007fb34cd599c2 n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x259c2)
#12 0x00007fb34cd5d372 n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x29372)
#13 0x00007fb34ddc8af6 PyObject_Call (libpython3.8.so.1.0 + 0x136af6)
#14 0x00007fb34ddb1a42 _PyEval_EvalFrameDefault (libpython3.8.so.1.0 + 0x11fa42)
#15 0x00007fb34ddae8b4 _PyEval_EvalCodeWithName (libpython3.8.so.1.0 + 0x11c8b4)
#16 0x00007fb34ddbccb3 _PyFunction_Vectorcall (libpython3.8.so.1.0 + 0x12acb3)
#17 0x00007fb34ddb00ea _PyEval_EvalFrameDefault (libpython3.8.so.1.0 + 0x11e0ea)
#18 0x00007fb34ddbcfaa n/a (libpython3.8.so.1.0 + 0x12afaa)
#19 0x00007fb34ddafd78 _PyEval_EvalFrameDefault (libpython3.8.so.1.0 + 0x11dd78)
#20 0x00007fb34ddbcfaa n/a (libpython3.8.so.1.0 + 0x12afaa)
#21 0x00007fb34ddafd78 _PyEval_EvalFrameDefault (libpython3.8.so.1.0 + 0x11dd78)
#22 0x00007fb34ddae8b4 _PyEval_EvalCodeWithName (libpython3.8.so.1.0 + 0x11c8b4)
#23 0x00007fb34ddae599 PyEval_EvalCodeEx (libpython3.8.so.1.0 + 0x11c599)
#24 0x00007fb34de2eaeb PyEval_EvalCode (libpython3.8.so.1.0 + 0x19caeb)
#25 0x00007fb34de39668 n/a (libpython3.8.so.1.0 + 0x1a7668)
#26 0x00007fb34de34003 n/a (libpython3.8.so.1.0 + 0x1a2003)
#27 0x00007fb34dd2e4a3 n/a (libpython3.8.so.1.0 + 0x9c4a3)
#28 0x00007fb34dd2dc47 PyRun_SimpleFileExFlags (libpython3.8.so.1.0 + 0x9bc47)
#29 0x00007fb34de463aa Py_RunMain (libpython3.8.so.1.0 + 0x1b43aa)
#30 0x00007fb34de220e9 Py_BytesMain (libpython3.8.so.1.0 + 0x1900e9)
#31 0x00007fb34daefb25 __libc_start_main (libc.so.6 + 0x27b25)
#32 0x0000560b3096507e _start (python3.8 + 0x107e)
Stack trace of thread 16585:
#0 0x00007fb34dbbdeaf __poll (libc.so.6 + 0xf5eaf)
#1 0x00007fb34cc3226e n/a (libglib-2.0.so.0 + 0x5526e)
#2 0x00007fb34cc3238f g_main_context_iteration (libglib-2.0.so.0 + 0x5538f)
#3 0x00007fb3344b059d n/a (libdconfsettings.so + 0x659d)
#4 0x00007fb34cc5b3ce n/a (libglib-2.0.so.0 + 0x7e3ce)
#5 0x00007fb34dab0299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007fb34dbc8cc3 __clone (libc.so.6 + 0x100cc3)
Stack trace of thread 16577:
#0 0x00007fb34dbbdeaf __poll (libc.so.6 + 0xf5eaf)
#1 0x00007fb34cc3226e n/a (libglib-2.0.so.0 + 0x5526e)
#2 0x00007fb34cc325cb g_main_loop_run (libglib-2.0.so.0 + 0x555cb)
#3 0x00007fb34ca0cb76 n/a (libgio-2.0.so.0 + 0x120b76)
#4 0x00007fb34cc5b3ce n/a (libglib-2.0.so.0 + 0x7e3ce)
#5 0x00007fb34dab0299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007fb34dbc8cc3 __clone (libc.so.6 + 0x100cc3)
Stack trace of thread 16575:
#0 0x00007fb34dbbdeaf __poll (libc.so.6 + 0xf5eaf)
#1 0x00007fb34cc3226e n/a (libglib-2.0.so.0 + 0x5526e)
#2 0x00007fb34cc3238f g_main_context_iteration (libglib-2.0.so.0 + 0x5538f)
#3 0x00007fb34cc323e1 n/a (libglib-2.0.so.0 + 0x553e1)
#4 0x00007fb34cc5b3ce n/a (libglib-2.0.so.0 + 0x7e3ce)
#5 0x00007fb34dab0299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007fb34dbc8cc3 __clone (libc.so.6 + 0x100cc3)
Maybe an issue in gobject upstream but gajim is the only one affected and I'm unlikely to debug it any further. This is extremely annoying and makes you miss messages. Likely has something to do with networking. Happens once in few hours.