gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"]

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

+1
It is impossible to use WebStrom, as Gnome-Shell on Ubuntu 19.10 constantly crashes

Hello,

I saw that the Merge Request that fixes this bug (https://gitlab.gnome.org/GNOME/mutter/merge_requests/895) has been merged to master already. Is there any chance that this will be applied to the ubuntu package of mutter in 19.10 soon?

I'd be interested in that as well. I'm using the text editor "Geany", and every time I use the search function, this exact same error happens for me. Hoping that the package in Ubuntu gets fixed soon.

+1

Hi, im also really looking forward to find this fix in ubuntu. Currently my Intellij is crashing steady. :( I also ask Jetbrains if they can provide a workaround but they told me that i have to wait for ubuntu. They cannot do that.

+1

Same here (https://youtrack.jetbrains.com/issue/IDEA-226221)... Also asked Jetbrains for workaround, also got as answer 'Go to Gnome and then to Ubuntu'. Hurray for closed source! For the time being a can not resume my normal workflow. Please apply the mutter fix!!

BTW, a little workaround: For me the crashes appeared most often in the commit dialog; you can disable the commit dialog and thus the crash by enabling the "Commit from Local Changes without showing the Commit dialog" option under "Version Control > Commit Dialog". I'm using PHPStorm 2019.2.5

Please publish a new version of the package with the fix included - this bug affects JetBrains IDEs which are widely used, and makes developing on Ubuntu 19.10 a frustrating experience.

This bug was fixed in the package mutter - 3.34.2-2ubuntu1

---------------
mutter (3.34.2-2ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + 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.34.2-2) unstable; urgency=medium

  * d/p/EGL-Include-EGL-eglmesaext.h.patch: Cherry pick from master. This
    fixes the generated EGL includes for the move of exlext.h from mesa to
    libglvnd, which has just happened in Debian.

mutter (3.34.2-1ubuntu1) focal; urgency=medium

  * Merge with debian including new upstream version 3.34.2 (LP: #1857037):
    - Fix an hang when using DisplayLink with Wayland (LP: #1853357)
    - Kill window effects on destroy (LP: #1844222)
    - Fixed a crash when using various Java apps such as Intellij (LP: #1845281)
    - Fixed a crash when handling X11 events (LP: #1846403)
    - Fixed some double-scaling in wayland
    - More crash and hang fixes
    Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + 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.34.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - d/libmutter-5-0.symbols: Update
    - d/copyright: Update
  * d/gbp.conf: Use upstream/3.34.x branch
  * Remove obsolete Lintian override
  * Standards-Version: 4.4.1 (no changes required)
  * d/tests: Use correct compiler for proposed autopkgtest
    cross-architecture testing support

 -- Iain Lane <email address hidden> Sun, 22 Dec 2019 17:24:36 +0000

Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.34.3-1ubuntu1~19.10.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 and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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.

Thanks! Have installed the package from eoan-proposed:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-=======================-============-===========================================================
ii mutter 3.34.3-1ubuntu1~19.10.1 amd64 Example window manager using GNOME's window manager library
ii mutter-common 3.34.3-1ubuntu1~19.10.1 all shared files for the Mutter window manager

Will do some testing and report back.

Hi folks,

I have now tested in the latest versions of both PyCharm (PyCharm 2019.3.1 (Professional Edition)
Build #PY-193.5662.61) and IntelliJ (2019.3.1 Ultimate Edition Build #IU-193.5662.53) and can (unfortunately) confirm that the issue continues to persist in both cases.

Happy to provide any further debug information if someone can tell me what to do.

Cheers,

Edd

Interesting. I tested that version as well, and all the (similar) crashing problems I had with the text editor Geany are gone, so the update at least seems to help in some cases.

Correction: The crashes still happen. I probably was just lucky when testing.

Yeah I've had a few false positives too. The problem definitely still persists for me.

using mutter Version: 3.34.3-1ubuntu1~19.10.1

I can systematically reproduce the crash with the following steps:

install intellij-idea
open a java project
press F4 to open project settings
select SDK
click + to add a new SDK and select JDK

In eoan I had this issue in PyCharm, but I was able to fix it by upgrading the proposed package today.

Jean, Edd an Florian:

Please open another bug since the crash you're getting is quite likely different from this one.

The error relative to this bug (https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684) has no reports for the 3.34.3 version at all, so I'm quite sure we're talking of a different crash.

Can you guys send me a crash trace following the instructions at https://is.gd/wiki_gnome_shell_crash_debug ?

Also, have you verified to have installed the right *mutter* version?

I recently reported the issue to jetbrains https://youtrack.jetbrains.com/issue/IDEA-233737
(with a screencast)

All packages: mutter, mutter-common, gir1.2-mutter-5 and libmutter-5-50
are at version 3.34.1+git20191107-1ubuntu1~19.10.1

journalctl log
-------------------------------
feb 25 12:20:29 delphy gnome-shell[9183]: **
feb 25 12:20:29 delphy gnome-shell[9183]: mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: Bail out! mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 ==
feb 25 12:20:29 delphy gnome-shell[9183]: GNOME Shell crashed with signal 6
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 ==
--------------------------------------------

Also attached the gdb.txt file produced with these instructions
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell

Hope it helps

Updating __just__ `mutter` to 3.34.3-1ubuntu1~19.10.1 did not work; I had to update `libmutter-5-0` too. If you're using the instructions given in the link in comment https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/comments/10 to disable automatic updates to proposed packages, then this will attempt to remove a couple of essential core libraries such as `gdm3`, so you will have to NOT pin them and then go:

`sudo apt-get install libmutter-5-0/eoan-proposed mutter/eoan-proposed`

Hi @laszlo-vandenhoek, thanks for your comment (#20).

I'm trying to install libmutter-5-0 using your command and I can see that apt is proposing to remove various packages as you've mentioned. I'm not clear how to proceed though, can I ask what you meant by "so you will have to NOT pin them"?

This bug is so frustrating, totally kills my workflow on a daily basis :-( has everything been stable for you since upgrading libmutter?

Cheers,

Edd

@eddgrant Sorry, I rushed my previous comment a bit. I'll elaborate below.

To start with the good news: upgrading libmutter to the proposed version has fixed the IntelliJ crash problem. I haven't had any trouble since.

I was referring to the article https://wiki.ubuntu.com/Testing/EnableProposed, referenced by @sil2100 in #10. It first instructs you how to enable proposed updates, and then, in the paragraph "Selective upgrading from proposed", to pin packages to their current versions (i.e. stable, not proposed), by creating `/etc/apt/preferences.d/proposed-updates` with this content:

```
Package: *
Pin: release a=eoan-proposed
Pin-Priority: 400
```

The article reads `xenial`, not `eoan`, but I'm assuming you made that substitution, because we're dealing with Ubuntu 19.10 here, not 18.04.

If you did all this, then that would prevent `apt upgrade` from upgrading ALL packages from `eoan-proposed`. That's good, because we're only interested in testing the fix for `mutter`, not the hundreds of other proposed packages. However, if you then continue to follow instructions from that same page, you would end up doing something like:

`sudo apt-get install mutter/eoan-proposed`

This won't work as intended, because the new version of mutter depends on new versions of some other stuff (like libmutter, probably), also in eoan-proposed, but apt won't see it because it has been pinned by the pin file you created. The proper way of going about this, then, is to:

- comment the contents of the `/etc/apt/preferences.d/proposed-updates` with #'s
- run `sudo apt-get install libmutter-5-0/eoan-proposed mutter/eoan-proposed`
- uncomment again, to make sure you won't cut yourself on the bleeding edge of some other update

Good luck!

Thanks for the detailed reply @laszlo-vandenhoek, that was really helpful.

I have now successfully upgraded to `libmutter-5-0` and have not had a single re-occurrence of the issue. Great stuff!

Thanks again!

Marking v-done per the comments in this bug - thanks for testing!

This bug was fixed in the package mutter - 3.34.3-1ubuntu1~19.10.1

---------------
mutter (3.34.3-1ubuntu1~19.10.1) eoan; urgency=medium

  * Backport to eoan (LP: #1858683)

mutter (3.34.3-1ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + 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.34.3-1) unstable; urgency=medium

  * New upstream release
    + Fix window recording on HiDPI
    + Fix top-left pixel being insensitive to clicks (LP: #1849135)

mutter (3.34.2-2ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + 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.34.2-2) unstable; urgency=medium

  * d/p/EGL-Include-EGL-eglmesaext.h.patch: Cherry pick from master. This
    fixes the generated EGL includes for the move of exlext.h from mesa to
    libglvnd, which has just happened in Debian.

mutter (3.34.2-1ubuntu1) focal; urgency=medium

  * Merge with debian including new upstream version 3.34.2 (LP: #1857037):
    - Fix an hang when using DisplayLink with Wayland (LP: #1853357)
    - Kill window effects on destroy (LP: #1844222)
    - Fixed a crash when using various Java apps such as Intellij (LP: #1845281)
    - Fixed a crash when handling X11 events (LP: #1846403)
    - Fixed some double-scaling in wayland
    - More crash and hang fixes
    Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + 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.34.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - d/libmutter-5-0.symbols: Update
    - d/copyright: Update
  * d/gbp.conf: Use upstream/3.34.x branch
  * Remove obsolete Lintian override
  * Standards-Version: 4.4.1 (no changes required)
  * d/tests: Use correct compiler for proposed autopkgtest
    cross-architecture testing support

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 08 Jan 2020 13:31:04 +0000

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.

Ubuntu 19.10, mutter-3.34.3-1ubuntu1~19.10.1 and still crash sometimes with IntelliJ

----------------------------------------------------------------------
apr 17 16:40:45 delphy gnome-shell[2612]: **
apr 17 16:40:45 delphy gnome-shell[2612]: mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: Bail out! mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: GNOME Shell crashed with signal 6
apr 17 16:40:45 delphy gnome-shell[2612]: == Stack trace for context 0x56084b40d3b0 ==
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Failed with result 'core-dump'.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Service has no hold-off time (RestartSec=0), scheduling restart.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session (session: ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session (session: ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopped GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Starting GNOME Shell on X11...

^^^
That looks like a different bug. Please report it by running:

  ubuntu-bug gnome-shell