Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

2022-03-15 Thread Robbie Harwood (frozencemetery)
Package: libglib2.0-0 Version: 2.70.4-1 Followup-For: Bug #1007226 X-Debbugs-Cc: rharw...@club.cc.cmu.edu The crash seems to be triggered by one particular message, which I've uploaded in case it helps: https://gist.github.com/frozencemetery/cc73375f628c6dbfdbb4834396db9a63 Be well, --Robbie

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

2022-03-15 Thread Robbie Harwood (frozencemetery)
Package: libglib2.0-0 Version: 2.70.4-1 Followup-For: Bug #1007226 X-Debbugs-Cc: rharw...@club.cc.cmu.edu > I think we will really need a backtrace with at least GLib debug symbols, > and preferably GMime too, so that we can tell what identifier we're trying > to parse here. (Or you could try

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

2022-03-14 Thread Simon McVittie
Control: tags -1 + moreinfo On Sun, 13 Mar 2022 at 22:15:44 -0400, Robbie Harwood (frozencemetery) wrote: > GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion > failed: (tz != NULL) The failing assertion is: /* Seemingly, we should be using @seconds directly to set

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

2022-03-13 Thread Robbie Harwood (frozencemetery)
Package: libglib2.0-0 Version: 2.71.3-1 Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, When running `notmuch new`, I get this error: ** GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL) Bail out!