On Sun, Jan 07, 2018 at 09:51:09PM +0000, Simon McVittie wrote: > tag 881301 pending > thanks > > Hello, > > Bug #881301 reported by you has been fixed in the Git repository. You can > see the changelog below, and you can check the diff of the fix at: > > > https://anonscm.debian.org/cgit/pkg-gnome/gnome-shell.git/commit/?id=63df168 > > --- > commit 63df1682ef0e62f1ce5e360411e18c52dd02562e > Author: Simon McVittie <s...@debian.org> > Date: Sun Jan 7 18:56:06 2018 +0000 > > Depend on gjs (>= 1.50.2-3~) > > So that using an object after it's destroyed doesn't crash the > Shell. Critical warnings will be logged instead, usually to the systemd > journal. Please report these as new bugs if seen: we can't tell from the > crash backtraces whether the bug was in the Shell itself or an extension, > which makes the existing bug reports unclear, but the critical warnings > should make it clearer where the bug is. (Closes: #881301, #880663; LP: > #1714989, LP: #1721321, LP: #1722986, LP: #1725015) > > diff --git a/debian/changelog b/debian/changelog > index a1dc9c1..31dfa7c 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -10,6 +10,14 @@ gnome-shell (3.26.2-3) UNRELEASED; urgency=medium > - Don't shadow ClutterActor's destroy() (GNOME #791233) > - Guard against malformed world-clocks settings (GNOME #791148) > - Don't leak fds when background changes (GNOME #791655) > + * Depend on gjs (>= 1.50.2-3~) so that using an object after it's > + destroyed doesn't crash the Shell. Critical warnings will be logged > + instead, usually to the systemd journal. Please report these as new > + bugs if seen: we can't tell from the crash backtraces whether the > + bug was in the Shell itself or an extension, which makes the existing > + bug reports unclear, but the critical warnings should make it clearer > + where the bug is. (Closes: #881301, #880663; LP: #1714989, > + LP: #1721321, LP: #1722986, LP: #1725015) > > -- Simon McVittie <s...@debian.org> Sun, 07 Jan 2018 17:32:25 +0000
When can this reach unstable? Somehow, I've started hitting this bug yesterday, and it's now happening any time I get back from screen locking. Meaning, if I go out for a minute, I'm just as good as if I had just rebooted. Mike
