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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2006981
Title:
apport-gtk crashed with signal
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2006981
Title:
apport-gtk crashed with signal 5 in g_log_writer_default()
4 matches
Mail list logo