gnome shell crashes upon maximizing a window after closing a restored window

[Nibl]

This is on Ubuntu Noble 24.04 with gnome-shell 46.0-0ubuntu5.1
The shell will crash if you do the following:

1. Open any two programs that can be maximized. To make reproduction as streamlined as possible, one of them should be Firefox or Steam.

2. Drag Firefox or Steam to the top of the screen to maximize it.

3. Click on empty space near the top of the maximized program until the program randomly restores itself. I do not mean the double click restore action. This itself is also a bug. It might take a few random clicks on Firefox but it will eventually happen.

4. Close the program that just restored its size.

5. Grab your second application and drag it to the top of the screen to maximize it.

6. Gnome shell will crash.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Nibl (graystripe)]

What I had done was purposely caused the crash, then looked in var/crash, and gnome-shell was the only thing generating crash logs. I can reliably reproduce the crash. What is the best way to capture the event?

[Nibl (graystripe)]

Doing step 2 and pressing send just closes the window and doesn't actually give me any output. I've done it twice now. The crash does not show up on the list of things after following step 3.

[Nibl (graystripe)]

I just reproduced the crash, and now step 3 yielded this:

https://errors.ubuntu.com/oops/0ae6e12e-3774-11ef-8bf5-fa163ec8ca8c

[Daniel van Vugt (vanvugt)]

Thanks, yes I can see that machine has only successfully sent one of the gnome-shell crash reports. Unfortunately there seems to be a secondary bug in either gnome-shell's logging or the crash reporter whereby we can't see the correct section of the system log. Only that gnome-shell crashed with some kind of assertion failure inside libmutter. I think it's most likely to be bug 2050865, but we should verify that.

Please run:

  journalctl -b0 > journal.txt
  journalctl -b-1 > prevjournal.txt

and attach the resulting text files here.

[Nibl (graystripe)]

I don't think that bug you linked is my problem because I'm running an X11 session and haven't plugged any external displays into the computer.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2068539, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.