[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Steve Langasek
'regression-update' is for regressions introduced in the -updates pocket of a stable release; removing the tag ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764216

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Daniel van Vugt
** Package changed: gjs (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764216 Title: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Daniel van Vugt
** Description changed: - EMERGENCY - Since Ubuntu updated to gjs 1.52.1-1, our bug tracking systems are unable to automatically retrace crashes. This has created a sudden wave of crash reports that we can't automatically classify. For example, this is what LP: #1748450/LP: #1505409 lo

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Daniel van Vugt
** Summary changed: - [regression] Unreadable stack traces since upgrading to gjs 1.52.1 + [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1

2018-04-15 Thread Daniel van Vugt
This report: https://errors.ubuntu.com/problem/7576bbf83cb88a0b3a870e1371dd86416b23c4b3 suggests the wave of unreadable stack traces this morning was perhaps due to an update to glib2.0, because: /lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.0 (deleted) So they are almost certainly all duplicates

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1

2018-04-15 Thread Daniel van Vugt
Although that doesn't make this bug invalid. ** Changed in: gjs (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764216 Title: [regression] Unreadable stack tra

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1

2018-04-15 Thread Daniel van Vugt
Actually, this looks like a new issue. We still see reports of LP: #1748450 with the old stack trace even with gjs 1.52.1-1 ** Changed in: gjs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. http

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1

2018-04-15 Thread Daniel van Vugt
Also tracking in: https://gitlab.gnome.org/GNOME/gjs/issues/145 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764216 Title: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 To ma