gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement()

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

---------------
mutter (41.3-1ubuntu1) jammy; urgency=medium

  * Merge with debian, includes these upstream changes:
    - window: Don't change workspaces of unmanaged windows (LP: #1933996)
    - backend: Reset idletime when unplugging the power cable (LP: #1945121)
    - clutter/text: Invalidate actor paint volume when it has changed
      (LP: #1882291)
    - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186)
    - OSK Enter, space and backspace keys don't work when typing in Greek
      (LP: #1820523)
    - window: Don't change workspaces of unmanaged windows (LP: #1932328)
  * Remainig changes with debian:
    - debian/gbp.conf: update upstream 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 (41.3-1) unstable; urgency=medium

  * New upstream release:
    - Check keyboard serials for activation
    - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535)
    - Allow disabling HW cursors
    - Improve damage handling (LP: #1872870)
    - Consider xrandr flags for advertised modes
    - Ensure constraints after client resize
    - window-group: Disable culling when rendinging clone to offscreen buffer
    - Fix workspace switch animation in default plugin
    - Fix unfullscreening of window that were mapped fullscreen
    - Fix DMA-BUF screencasts with unredirected fullscreen windows
    - Fix orientation changes on devices with 90°

mutter (41.2-2) unstable; urgency=medium

  * Team upload
  * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch:
    Add proposed patch to fix FTBFS on 32-bit architectures
  * d/patches: Update to 41.2-6-g7b64c159a
    - Surface damage viewport improvements
  * Update patch metadata with upstream status

mutter (41.2-1) unstable; urgency=medium

  * Team upload

  [ Simon McVittie ]
  * New upstream release
  * d/patches: Drop patches that were applied upstream
  * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631
    - wayland: Check keyboard serials for activation
    - Sync refresh rate to the correct monitor for maximized/full-screen
      apps in a multi-monitor layout
    - Add a debug environment variable to disable hardware cursors for
      faulty hardware and drivers

  [ Laurent Bigonville ]
  * debian/rules: Disable systemd support on non-linux architectures

mutter (41.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Drop a patch that came from upstream
  * Update Lintian overrides
  * Replace patches for #995929 with the version that was applied upstream
  * Remove workaround for #994806
  * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into.
    Nothing else in Debian references this symbol, except for forks of
    the mutter codebase.

mutter (41.0-5) unstable; urgency=medium

  * Team upload
  * Merge packaging from unstable
    - No changes relative to 41.0-4, except for the changelog
  * Close #995929 via changelog.
    The patches in 41.0-4 seem to have been successful.
  * Release to...

Just crashed with mutter 41.3-3ubuntu1

https://errors.ubuntu.com/oops/6ced385f-9879-11ec-8797-fa163ee63de6

Fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2711 but that's only in mutter 44 (main) right now.

Fedora bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2147502
https://bugzilla.redhat.com/show_bug.cgi?id=1983946

In relation with bug 2004111 that I submitted which was flagged as a duplicate of this one, it just happenned again and I think I noticed that it only happens when I have applications open, if no applications are running it seems that my session doesn't close. I thought I'd share in case it can help to fix the bug.

Here's the link for my latest occurence that just happened:

https://errors.ubuntu.com/oops/cbed6a7a-a4b4-11ed-abd1-fa163e55efd0
https://errors.ubuntu.com/oops/c99be648-a4b4-11ed-b7d7-fa163ef35206

Also sorry for not being as well versed in Ubuntu bug fix process, but from what I understand when the status will be 'Fix Released' for my version of Ubuntu then I can just apt update && apt upgrade to get the fix?

Thanks

Yes the first link there is this bug. The second link is bug 1842439.

And yes you should be watching the 'Jammy' line at the top of this page. After it reaches 'Fix Released' the update will roll out in a staggered way to a limited number of users, and more users over time. If you want to get it sooner at that time then you will be able to find the link to the updated deb files and download them manually.

Thanks for the clarification, however just to make sure whenever I experience this behavior, both bugs are reported together every time.

Still happening in GNOME 44 (bug 2015473) !?

Confirmed multiple reports of the crash still happening in GNOME 44 so we don't have a reliable fix coming.