It would be an easy fix if the assertion message printed the backtrace of the apps calling in glib.
I wonder if the system packages are compiled in RelWithDbgInfo by default, so that a stacktrace would be useful in release for fixing bugs like this. I wonder if there's a way to extend G_DEBUG with a "slient- stacktraces" option that would report a core file to the system on each critical/warning, because I assume it's in Ubunutu's best interests to fix all of these they can, but of course you don't want all the apps crashing, so G_DEBUG=fatal-criticals doesn't seem it will work. (Very much a newbie to Ubuntu and GNOME, just wondering...) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1740522 Title: GLib: g_variant_new_string: assertion 'string != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1740522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
