Database Migration CoreDump
Daemon Commit: 6b392ef15ee856e7437864911a409a2db166ac55
LRC commit: 1be57bd503cd43501ac08eb26c5bdc096e393d76
Gnome commit: 1faed4b9
Referencing https://git.jami.net/savoirfairelinux/ring-client-android/issues/644
Oct 14 13:14:54 computerName systemd-coredump[791952]: Process 790516 (jami-gnome) of user 1000 dumped core.
Stack trace of thread 790516:
#0 0x000075e1f69a3f25 raise (libc.so.6)
#1 0x000075e1f698d897 abort (libc.so.6)
#2 0x000075e1f6d2781d _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6)
#3 0x000075e1f6d344da _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6)
#4 0x000075e1f6d34537 _ZSt9terminatev (libstdc++.so.6)
#5 0x000075e1f6d3478d __cxa_throw (libstdc++.so.6)
#6 0x000075e1fd886ce2 _ZNK3lrc3api7AVModel17getDeviceSettingsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE.cold (libringclient.so.1.0.0)
#7 0x000075e1fd94df1c _ZN3lrc12AVModelPimplC1ERNS_3api7AVModelERKNS_16CallbacksHandlerE (libringclient.so.1.0.0)
#8 0x000075e1fd94e8cc _ZN3lrc3api7AVModelC1ERKNS_16CallbacksHandlerE (libringclient.so.1.0.0)
#9 0x000075e1fd911d6a _ZN3lrc8LrcPimplC1ERNS_3api3LrcERSt8functionIFvvEES7_ (libringclient.so.1.0.0)
#10 0x000075e1fd911e0b _ZN3lrc3api3LrcC2ESt8functionIFvvEES4_ (libringclient.so.1.0.0)
#11 0x0000588e2c2f4b97 make_unique<lrc::api::Lrc, (anonymous namespace)::details::CppImpl::CppImpl(RingMainWindow&)::<lambda()>, (anonymous namespace)::details::CppImpl::CppImpl(RingMainWindow&)::<lambda()> > (jami-gnome)
#12 0x0000588e2c2e72c9 CppImpl (jami-gnome)
#13 0x0000588e2c2f4282 ring_main_window_init (jami-gnome)
#14 0x000075e1fc952340 g_type_create_instance (libgobject-2.0.so.0)
#15 0x000075e1fc96e746 n/a (libgobject-2.0.so.0)
#16 0x000075e1fc96f2f9 g_object_new_valist (libgobject-2.0.so.0)
#17 0x000075e1fc96fc6a g_object_new (libgobject-2.0.so.0)
#18 0x0000588e2c2f4ae1 ring_main_window_new (jami-gnome)
#19 0x0000588e2c2df4dc ring_client_activate (jami-gnome)
#20 0x000075e1fc95bb4a g_signal_emit_valist (libgobject-2.0.so.0)
#21 0x000075e1fc95c7f0 g_signal_emit (libgobject-2.0.so.0)
#22 0x000075e1fca32e09 n/a (libgio-2.0.so.0)
#23 0x000075e1fca32946 g_application_run (libgio-2.0.so.0)
#24 0x0000588e2c2ddfbe main (jami-gnome)
#25 0x000075e1f698f153 __libc_start_main (libc.so.6)
#26 0x0000588e2c2ddd6e _start (jami-gnome)
Stack trace of thread 790518:
#0 0x000075e1f6a5c9ef __poll (libc.so.6)
#1 0x000075e1fc87f180 n/a (libglib-2.0.so.0)
#2 0x000075e1fc87f251 g_main_context_iteration (libglib-2.0.so.0)
#3 0x000075e1fd9e1e5e n/a (libdconfsettings.so)
#4 0x000075e1fc85bc11 n/a (libglib-2.0.so.0)
#5 0x000075e1f68b54cf start_thread (libpthread.so.0)
#6 0x000075e1f6a672d3 __clone (libc.so.6)
Stack trace of thread 790517:
#0 0x000075e1f6a5c9ef __poll (libc.so.6)
#1 0x000075e1fc87f180 n/a (libglib-2.0.so.0)
#2 0x000075e1fc87f251 g_main_context_iteration (libglib-2.0.so.0)
#3 0x000075e1fc87f2a2 n/a (libglib-2.0.so.0)
#4 0x000075e1fc85bc11 n/a (libglib-2.0.so.0)
#5 0x000075e1f68b54cf start_thread (libpthread.so.0)
#6 0x000075e1f6a672d3 __clone (libc.so.6)
Stack trace of thread 790520:
#0 0x000075e1f68bbc45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x000075e1eac434fc n/a (i965_dri.so)
#2 0x000075e1eac430f8 n/a (i965_dri.so)
#3 0x000075e1f68b54cf start_thread (libpthread.so.0)
#4 0x000075e1f6a672d3 __clone (libc.so.6)
Stack trace of thread 790521:
#0 0x000075e1f6a5c9ef __poll (libc.so.6)
#1 0x000075e1fc87f180 n/a (libglib-2.0.so.0)
#2 0x000075e1fc87f251 g_main_context_iteration (libglib-2.0.so.0)
#3 0x000075e1fc5eea03 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4 0x000075e1fc5954ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x000075e1fc3c7385 _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x000075e1f68e3b37 n/a (libQt5DBus.so.5)
#7 0x000075e1fc3c85b0 n/a (libQt5Core.so.5)
#8 0x000075e1f68b54cf start_thread (libpthread.so.0)
#9 0x000075e1f6a672d3 __clone (libc.so.6)
Stack trace of thread 790519:
#0 0x000075e1f6a5c9ef __poll (libc.so.6)
#1 0x000075e1fc87f180 n/a (libglib-2.0.so.0)
#2 0x000075e1fc880123 g_main_loop_run (libglib-2.0.so.0)
#3 0x000075e1fc9efb48 n/a (libgio-2.0.so.0)
#4 0x000075e1fc85bc11 n/a (libglib-2.0.so.0)
#5 0x000075e1f68b54cf start_thread (libpthread.so.0)
#6 0x000075e1f6a672d3 __clone (libc.so.6)
Stack trace of thread 790650:
#0 0x000075e1f6a5c9ef __poll (libc.so.6)
#1 0x000075e1e8983c14 n/a (libpulse.so.0)
#2 0x000075e1e8991059 pa_mainloop_poll (libpulse.so.0)
#3 0x000075e1e899b301 pa_mainloop_iterate (libpulse.so.0)
#4 0x000075e1e899b3b1 pa_mainloop_run (libpulse.so.0)
#5 0x000075e1e898b61e n/a (libpulse.so.0)
#6 0x000075e1e890fd1c n/a (libpulsecommon-13.0.so)
#7 0x000075e1f68b54cf start_thread (libpthread.so.0)
#8 0x000075e1f6a672d3 __clone (libc.so.6)
This occurred after the log message:
Oct 14 13:06:13 computerName jami-gnome[790516]: Can't open file: "/home/userName/.local/share/jami/Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken./profile.vcf"
...
Oct 14 13:14:08 computerName audit[790516]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=790516 comm="jami-gnome" exe="/usr/local/bin/jami-gnome" sig=6 res=1
That's about 9 minutes between the log entries.
EDIT0:
The second time of trying to open it, there was NO window, but the process was still up and working with the same log message as ".../profile.vcf" mentioned before, and then the coredump came.
EDIT1:
I ran lsof to find anything having the vcf locked, or anything related to jami, but nothing was found (after the coredump).
BUT... looking in ./local/share/jami, I see a folder NAMED "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Yes, really.