Little bit of data here. For some reason glib2.0 is thinking we're in a GDB context and so is spitting out a SIGTRAP rather than the expected SIGABRT, see https://sources.debian.org/src/glib2.0/2.78.3-1/glib/gmessages.c/#L556
Now, why is it aborting I'm not too sure. The stack trace gives us a hint, as it seems it's failing to detect a graphical environment.
Did the crash appear spontaneously on the desktop, or were you trying to report another bug?
Little bit of data here. For some reason glib2.0 is thinking we're in a GDB context and so is spitting out a SIGTRAP rather than the expected SIGABRT, see https:/ /sources. debian. org/src/ glib2.0/ 2.78.3- 1/glib/ gmessages. c/#L556
Now, why is it aborting I'm not too sure. The stack trace gives us a hint, as it seems it's failing to detect a graphical environment.
Did the crash appear spontaneously on the desktop, or were you trying to report another bug?