GLib-CRITICAL g_key_file_set_string: assertion 'string != NULL' failed

[konomikitten]

Profanity contains the following errors in ~/.local/share/profanity/logs/profanity.log

2024-06-13T18:31:02.839692+10: stderr: ERR:
2024-06-13T18:31:02.839766+10: stderr: ERR: (profanity:62979): GLib-CRITICAL **: 18:31:02.833: g_key_file_set_string: assertion 'string != NULL' failed

Environment

$ profanity -v
Profanity, version 0.14.0
Copyright (C) 2012 - 2019 James Booth <[email protected]>.
Copyright (C) 2019 - 2023 Michael Vetter <[email protected]>.
License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Build information:
XMPP library: libstrophe
Desktop notification support: Enabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.18.0)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.11.9)
GTK icons/clipboard: Enabled
GDK Pixbuf: Enabled

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ dpkg-query --show --showformat='${binary:Package} ${Version}\n' profanity libstrophe0 libglib2.0-0t64
libglib2.0-0t64:amd64 2.80.3-1
libglib2.0-0t64:i386 2.80.3-1
libstrophe0:amd64 0.13.1-1
profanity 0.14.0-1+b2

[jubalh]

Those glib messages can just be gibberish. Sometimes we want to insert nothing.

Do you know when this happened? Was there any setting not saved?

[konomikitten]

I have no clue I know it occurs on both my desktop and laptop both are Debian Unstable.

[jubalh]

Then I think there is nothing wrong here.
This just happens when you set a setting to nothing and we insert NULL. Probably a value ?: "" would be good to surpress this bogus message though.