[Touch-packages] [Bug 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()

2024-01-05 Thread Simon Chopin
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

[Touch-packages] [Bug 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()

2023-04-20 Thread Launchpad Bug Tracker
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.

[Touch-packages] [Bug 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()

2023-04-11 Thread Benjamin Drung
** 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

[Touch-packages] [Bug 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()

2023-04-11 Thread Benjamin Drung
** 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()