gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 g_assertion_message.cold () from /tmp/apport_sandbox_3x1xvo90/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_assertion_message_expr () from /tmp/apport_sandbox_3x1xvo90/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 meta_x11_get_stage_window (stage=<optimized out>) at ../src/backends/x11/meta-stage-x11.c:872

Status changed to 'Confirmed' because the bug affects multiple users.

Tracking in: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

This bug was fixed in the package mutter - 3.36.4-1ubuntu1

---------------
mutter (3.36.4-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream stable release, remaining changes:
    - debian/control:
      + Update VCS flags to point to ubuntu salsa branch
    - debian/gbp.conf: update branch to point to ubuntu/master
    - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr
  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
    - Remove ubuntu-only private symbol

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
    - Fix crash on area screenshots with fractional scaling
    - Do not paint textures of fully obscured windows
    - Turn off CRTCs as well when enabling DPMS
    - Improve selection support
    - Use a more appropriate combine function on opaque areas
    - Fix remote desktop being broken without screencast session
    - Fix popovers disappearing on wayland and HiDPI
    - Fixed crashes (LP: #1870867, LP: #1857947)
    - Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
    d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
    d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
    d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
    d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
    d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
    d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
    d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-1000000.patch,
    d/p/screen-cast-window-stream-src-Fix-indentation.patch:
    - Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 20 Jul 2020 15:45:20 +0200

Hello Ivan, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hi Brian,

I installed the proposed package and tried to test this. My results were mixed. I used the touchscreen for a while without issues. But then xorg crashed (and this report was a crash in gnome-shell). Apport refused to submit the bug reports because apparently there were a few not-updated packges (there weren't yesterday).

I think that's a different issue than this original report, but it's still a crash when using the touchscreen.

I'll re-update all my packages and keep testing.

I ran another test of using the touchscreen and managed to make gnome-shell crash. It looks like apport uploaded it this time, but I couldn't figure out where it put it. I attached the *.uploaded file associated with the reproduction. There's some other files in /var/crash, but I guess they should have already been uploaded. Let me know if I should upload them.

Ivan, the *.crash files are those with more informations.

Were you running gnome-shell from proposed repository?

I have mutter from proposed, and I don't see any newer version of gnome-shell in the proposed repository.

I've attached the crash file as well. Also, I'm not really sure if the crash I reproduced is about this bug or not. I've had other crashes that were filed separately and have different stack traces but were caused by using the touchscreen also, such as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861542

Just in case, here's the actual versions:

sibrus@poseidon:~/tmp$ dpkg --list | grep mutter
ii gir1.2-mutter-6:amd64 3.36.3-0ubuntu0.20.04.1 amd64 GObject introspection data for Mutter
ii libmutter-6-0:amd64 3.36.3-0ubuntu0.20.04.1 amd64 window manager library from the Mutter window manager
ii mutter 3.36.4-0ubuntu0.20.04.1 amd64 Example window manager using GNOME's window manager library
ii mutter-common 3.36.4-0ubuntu0.20.04.1 all shared files for the Mutter window manager

sibrus@poseidon:~/tmp$ dpkg --list | grep gnome-shell
ii chrome-gnome-shell 10.1-5 all GNOME Shell extensions integration for web browsers
ii gnome-shell 3.36.3-1ubuntu1~20.04.2 amd64 graphical shell for the GNOME desktop
ii gnome-shell-common 3.36.3-1ubuntu1~20.04.2 all common files for the GNOME graphical shell

Mh, I've tried to inspect that crash file, but it looks like that the core-dump it contains isn't complete enough as I can't get the symbols on it:

warning: Unexpected size of section `.reg-xstate/4998' in core file.
#0 __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: File o directory non esistente.
[Current thread is 1 (Thread 0x7f2e7a72fcc0 (LWP 4998))]
(gdb) bt
#0 __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x000055f2fef3752a in dump_gjs_stack_on_signal_handler (signo=6) at ../src/main.c:421
#2 <signal handler called>
#3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#4 0x00007f2e7fa8b859 in __GI_abort () at abort.c:79
#5 0x00007f2e808aeb63 in ?? ()
#6 0x00007ffe00303738 in ?? ()
#7 0x05b53dd8ea0b9800 in ?? ()
#8 0x000055f2ff3ae310 in ?? ()
#9 0x00007f2e7fda0c44 in ?? ()
#10 0x00007f2e8093d7c1 in ?? ()
#11 0x05b53dd8ea0b9800 in ?? ()
#12 0x000055f307c4a9b0 in ?? ()
#13 0x000055f3028399d0 in ?? ()
#14 0x00007f2e7fd9ed3b in ?? ()
#15 0x00007f2e7fda0c60 in ?? ()
#16 0x0000000000000366 in ?? ()
#17 0x00007f2e8090bb4f in ?? ()
#18 0x0000000000000000 in ?? ()
(gdb) sharedlibrary mutter
Symbols already loaded for /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
Symbols already loaded for /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-pango-6.so.0
Symbols already loaded for /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-6.so.0
Symbols already loaded for /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-path-6.so.0
(gdb)

---

However, are you sure we're talking of the same crash?
As so far, we've not got any crash with the same signature of this bug in errors.ubuntu.com

I switched to proposed and I have not had the bug appear. I used to experience it every 10 minutes or so when scrolling with my finger in Firefox and Chrome.

Now if we can only fix the bug where the on-screen keyboard appears when a physical keyboard is plugged in (grin).

Hello Ivan, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Marking this as verified, as it was properly reported as fixed in previous version (via https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/15) which doesn't change anything related to this bug.

Also no e.u.c failure has been recorded so far.

I am still getting this bug with the proposed version. Ubuntu 20.04 on a Lenovo machine.

I hope I updated correctly, I followed the instructions linked above to activate the "proposed" repository and installed the package with "sudo apt install mutter/focal-proposed", then deactivated the "proposed" repository and rebooted my machine. For the record, "dpkg --status mutter" shows "Version: 3.36.4-0ubuntu0.20.04.2", so I think I did it correctly. I did not touch gnome-shell. "gnome-shell --version" shows 3.36.3.

I used the touchscreen and triggered the bug after just a few minutes. gnome-shell crashed and some familiar messages were dumped in the syslog:

Aug 11 10:51:24 c930 gnome-shell[5197]: Object Meta.BackgroundActor (0x55be2f3b63f0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Aug 11 10:51:24 c930 gnome-shell[5197]: == Stack trace for context 0x55be2bb6a6f0 ==
Aug 11 10:51:24 c930 gnome-shell[5197]: #0 7fff7da0d270 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (2255897b6c40 @ 25)
Aug 11 10:51:24 c930 gnome-shell[5197]: #1 55be2caa60a0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (2ec7edda91f0 @ 85)
Aug 11 10:51:24 c930 gnome-shell[5197]: #2 55be2caa6018 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (2ec7edda4f88 @ 12)
Aug 11 10:51:24 c930 gnome-shell[5197]: JS ERROR: Error: Argument 'instance' (type interface) may not be null#012_init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24#012_onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45#012_init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44
Aug 11 10:51:24 c930 gnome-shell[5197]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed
Aug 11 10:51:27 c930 gnome-shell[5197]: **
Aug 11 10:51:27 c930 gnome-shell[5197]: mutter:ERROR:../src/backends/x11/meta-stage-x11.c:870:meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Aug 11 10:51:27 c930 gnome-shell[5197]: Bail out! mutter:ERROR:../src/backends/x11/meta-stage-x11.c:870:meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Aug 11 10:51:27 c930 gnome-shell[5197]: GNOME Shell crashed with signal 6
Aug 11 10:51:27 c930 gnome-shell[5197]: == Stack trace for context 0x55be2bb6a6f0 ==
Aug 11 10:51:41 c930 whoopsie-upload-all[7230]: Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash...
Aug 11 10:51:41 c930 whoopsie-upload-all[7230]: Marking /var/crash/_usr_bin_gnome-shell.1000.crash for whoopsie upload
Aug 11 10:51:41 c930 whoopsie[2089]: [10:51:41] Parsing /var/crash/_usr_bin_gnome-shell.1000.crash.
Aug 11 10:51:42 c930 whoopsie[2089]: [10:51:41] Uploading /var/crash/_usr_bin_gnome-shell.1000.crash.
Aug 11 10:51:42 c930 systemd[2217]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT
Aug 11 10:51:42 c930 systemd[2217]: gnome-shell-x11.service: Failed with result 'core-dump'.
Aug 11 10:5...

The automated error tracker is showing zero users have experienced the crash in 3.36.4 so it's possible you don't have the new package installed properly. But it's also possible it's an error that doesn't get reported reliably...

Please:

1. Make sure you have rebooted; and

2. Run 'dpkg -l' to show us your full package listing if it still happens.

Also please make sure you have no extensions other than the Ubuntu ones enabled. Look in the 'Extensions' app to check.

I rebooted and disabled all extensions other than the Built-in ones. I'm still able to trigger the crash. Output of dpkg -l is attached.

Good news Jack J, you just haven't installed it properly.

You upgraded your 'mutter' package to 3.36.4 but not your 'libmutter' package. It's the latter that gnome-shell uses and yours is still 3.36.3.

That is good news! I've been using the touchscreen as much as possible since last night and have been unable to reproduce the crash.

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---------------
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
    - Fix crash on area screenshots with fractional scaling
    - Do not paint textures of fully obscured windows
    - Turn off CRTCs as well when enabling DPMS
    - Improve selection support
    - Use a more appropriate combine function on opaque areas
    - Fix remote desktop being broken without screencast session
    - Fix popovers disappearing on wayland and HiDPI
    - Fixed crashes (LP: #1870867, LP: #1857947)
    - Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
    d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
    d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
    d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
    d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
    d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
    d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
    d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-1000000.patch,
    d/p/screen-cast-window-stream-src-Fix-indentation.patch:
    - Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
    - Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
    - Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
      LP: #1873403)
    - Decouple the output mode from layout mode capabilities (LP: #1876894,
      LP: #1886996)
    - Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
    - Apply proper layout monitor config when using fractional scaling
      (LP: #1884754)
    - Restore the fractional settings when reverting to fractional layout
      (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 27 Jul 2020 17:04:41 +0200

The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Hello Ivan, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and opened by the SRU tool as it is included again in the changelog as it's being part of a debian release we've merged with.

So marking as verified (as discussed with SRU team)

Hello Ivan, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

As per comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/27

We can mark this as verified.

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---------------
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
    Looks like this change (introduced to fix LP:1889090) got lost while
    rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
    - Refresh patches and drop applied ones
    - Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
    - Cherry-pick upstream night-switch fixes for 3.36 branch
    - Cherry-pick upstream fixes for handling X11 devices removal
      (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
    (LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
    - debian/control:
      + Update VCS flags to point to ubuntu salsa branch
    - debian/gbp.conf: update branch to point to ubuntu/master
    - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
    Now that we have Pipewire 0.3, we can enable screencasting and remote
    desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - Screencast fixes and improvements
    - Fix glitches when subsurfaces extend outside the toplevel
    - Improve background display in overview workspace switcher
    - Fix wine copy & paste
    - Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
    - Fix crash on area screenshots with fractional scaling
    - Do not paint textures of fully obscured windows
    - Turn off CRTCs as well when enabling DPMS
    - Improve selection support
    - Use a more appropriate combine function on opaque areas
    - Fix remote desktop being broken without screencast session
    - Fix popovers disappearing on wayland and HiDPI
    - Fixed crashes (LP: #1870867, LP: #1857947)
    - Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
    d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
    d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
    d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
    d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
    d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
    d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
    d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-1000000.patch,
    d/p/screen-cast-window-stream-src-Fix-indentation.patch:
    - Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 23 Sep 2020 22:03:53 +0200