gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] from windowPreview.js

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/be5b3f189bba5293ce040f812f28644f7ba22e17 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Daniel van Vugt (vanvugt)]

This crash looks fairly uncommon. It might also be related to an extension. Can anyone tell?

[Daniel van Vugt (vanvugt)]

Possibly related to https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4957

[Heather Ellsworth (hellsworth)]

I wonder if this is the same thing I just saw: https://paste.ubuntu.com/p/GSWYFy4jYh/

Or if it's not the same thing, I wonder if it is related. Also a clutter_acto_set_mapped: assertion failed crash. I have a crash log too, if you'd like to take a look.

[Daniel van Vugt (vanvugt)]

Comment #3 sounds like

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5197
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5137
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3165

and the fix hasn't landed yet:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2299

That should fix most recent occurrences of the crash. I'm not so sure about older releases though. The stack trace here is a little too terse so it will catch-all for other similar crashes too.

[Daniel van Vugt (vanvugt)]

The issue in comments #3 and #4 has moved to bug 1965557.

Although many people experiencing that bug may be led here by automated crash reports, we can't use this bug for it because the JavaScript stack traces from automated reports are often missing and don't factor into the errors.ubuntu.com bucket selection.