Critical triggered by account unknown to chatty
I'm seeing a long list of criticals on startup with
** (sm.puri.Chatty:4848): CRITICAL **: 09:05:03.092: purple_presence_set_status_active: assertion 'status != NULL' failed
Thread 1 "chatty" received signal SIGTRAP, Trace/breakpoint trap.
_g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
554 ../../../glib/gmessages.c: No such file or directory.
(gdb) bt
#0 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#1 0x00007ffff7c83869 in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7fffffffd440) at ../../../glib/gmessages.c:1373
#2 0x00007ffff7c83a2f in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>) at ../../../glib/gmessages.c:1415
#3 0x00007ffff70f825f in purple_buddy_new (account=account@entry=0x555555908c00, name=name@entry=0x555555a4e920 "sip:xyz@example.com", alias=alias@entry=0x555555986870 "xzy")
at ././libpurple/blist.c:1382
#4 0x00007ffff70facc9 in parse_buddy (bnode=0x5555559b9bb0, contact=0x5555559869a0, group=0x5555559868b0) at ././libpurple/blist.c:491
#5 parse_contact (cnode=0x5555559b9ab0, group=0x5555559868b0) at ././libpurple/blist.c:521
#6 parse_group (groupnode=0x5555559b9650) at ././libpurple/blist.c:599
#7 purple_blist_load () at ././libpurple/blist.c:623
#8 0x00005555555746e8 in chatty_manager_purple (self=0x555555625970 [ChattyManager]) at ../src/chatty-manager.c:1996
#9 0x00005555555762f5 in chatty_application_startup (application=0x555555628240 [ChattyApplication]) at ../src/chatty-application.c:275
#10 0x00007ffff7d67206 in _g_closure_invoke_va (closure=0x555555633910, return_value=0x0, instance=0x555555628240, args=0x7fffffffd850, n_params=0, param_types=0x0) at ../../../gobject/gclosure.c:873
#11 0x00007ffff7d858d4 in g_signal_emit_valist (instance=0x555555628240, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffffffd850) at ../../../gobject/gsignal.c:3407
#12 0x00007ffff7d85edf in g_signal_emit (instance=instance@entry=0x555555628240, signal_id=<optimized out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
#13 0x00007ffff7e8d7d2 in g_application_register (error=0x7fffffffd980, cancellable=0x0, application=0x555555628240 [ChattyApplication]) at ../../../gio/gapplication.c:2204
#14 g_application_register (application=0x555555628240 [ChattyApplication], cancellable=0x0, error=0x7fffffffd980) at ../../../gio/gapplication.c:2176
#15 0x00007ffff7e8db8a in g_application_real_local_command_line (application=0x555555628240 [ChattyApplication], arguments=0x7fffffffd9e8, exit_status=0x7fffffffd9e4) at ../../../gio/gapplication.c:1106
#16 0x00007ffff7e8df0a in g_application_run (application=0x555555628240 [ChattyApplication], argc=<optimized out>, argv=<optimized out>) at ../../../gio/gapplication.c:2528
#17 0x000055555556b03e in main (argc=1, argv=0x7fffffffdb68) at ../src/main.c:38
this is triggered by contacts of an account that is unknown to chatty. Can we somehow skip loading buddies from accounts that chatty does not know about? The blist.xml has the necessary information.