Your message dated Wed, 27 May 2020 10:19:51 +0100 with message-id <[email protected]> and subject line Re: Bug#955482: mutter aborts with "clutter-offscreen-effect.c:261:clutter_offscreen_effect_pre_paint: code should not be reached" has caused the Debian Bug report #955482, regarding mutter aborts with "clutter-offscreen-effect.c:261:clutter_offscreen_effect_pre_paint: code should not be reached" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 955482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955482 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mutter Version: 3.34.4-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was using gnome-shell, on wayland, with a terminal, emacs and epiphany (playing a youtube video). Out of the blue, the session broke and got the gdm login screen. I checked the journal and found this Mar 31 15:33:10 miau gnome-shell[1503]: Clutter:ERROR:../clutter/clutter/clutter-offscreen-effect.c:261:clutter_offscreen_effect_pre_paint: code should not be reached Mar 31 15:33:10 miau gnome-shell[1503]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-offscreen-effect.c:261:clutter_offscreen_effect_pre_paint: code should not be reached Mar 31 15:33:10 miau gnome-shell[1503]: == Stack trace for context 0x5627fc97c330 == Mar 31 15:33:10 miau systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 31 15:33:10 miau systemd[1]: Started Process Core Dump (PID 21845/UID 0). * What exactly did you do (or not do) that was effective (or ineffective)? I looked for error in mutter's gitlab and found this report which is similar: https://gitlab.gnome.org/GNOME/mutter/-/issues/808 And this merge request that fixes it https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1147 I rebuild the mutter package with this patch, which applied without problems, and now I'm running it. It seems to solve the problem. * What was the outcome of this action? * What outcome did you expect instead? I guess, for debian testing I would either add this patch in the build, or upgrade to 1.36. Thanks :) vmjl *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-debug'), (500, 'stable'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mutter depends on: ii gnome-settings-daemon-common 3.36.0-1 ii gsettings-desktop-schemas 3.36.0-1 ii libc6 2.30-2 ii libgles2 1.3.1-1 ii libglib2.0-0 2.64.1-1 ii libmutter-5-0 3.34.4-1 ii libwayland-server0 1.18.0-1 ii libx11-6 2:1.6.9-2 ii libxcomposite1 1:0.4.4-2 ii mutter-common 3.34.4-1 ii zenity 3.32.0-5 mutter recommends no packages. Versions of packages mutter suggests: ii gnome-control-center 1:3.36.0-1 ii xdg-user-dirs 0.17-2 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.36.1-1 On Wed, 01 Apr 2020 at 12:50:47 +0100, Simon McVittie wrote: > On Wed, 01 Apr 2020 at 13:16:22 +0200, Víctor M. Jáquez L. wrote: > > I looked for error in mutter's gitlab and found this report which is > > similar: > > > > https://gitlab.gnome.org/GNOME/mutter/-/issues/808 > > > > And this merge request that fixes it > > > > https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1147 > > This is not included in 3.36.0 (currently in experimental) so 3.36.0 > likely has this bug too. > > 3.36.1 (which is in gnome-team git, but not yet tested or released) > does include that change. This is believed to have been fixed a while ago by the upload of 3.36.1, first to experimental and then later to unstable/testing. smcv
--- End Message ---
