gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)

[Michel PIGUEL]

Hi,
I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears.
It seems to myself there is an issue between Wayland and spice-vdagent.
Regards,
Michel

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 29 09:52:12 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-01-28 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44
 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80
 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91
 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
 __GI_abort () at abort.c:79
Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44
 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80
 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91
 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
 __GI_abort () at abort.c:79

[Daniel van Vugt (vanvugt)]

I can't tell what assertion is failing here. The last message in the log is:

  meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

but that's just a warning which should never be fatal. That said, bug 1871262 fails to make the distinction too.

We need another crash report, better debug symbols or retracing here. Otherwise we can just call it a duplicate of bug 1871262 which itself is a little inaccurate.

[Apport retracing service (apport)]

StacktraceTop:
 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44
 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80
 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91
 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
 __GI_abort () at abort.c:79

[Daniel van Vugt (vanvugt)]

Looks like this crash has been fixed twice in the past:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4522

but all those fixes are in gnome-shell 41 already. So we need a new fix.

[Launchpad Janitor (janitor)]

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

[Zingam (registrirayme)]

Crashed on login. I tried to login once. Nothing happened. Then again.
I have a hybrid Intel+Nvidia laptop. I also heard sounds coming from my laptops speakers and they should come from my HDMI audio device usually (I haven't noticed that before). If that's an indication. After the login the sounds started coming out the the HDMI device.

I have set my external HDMI monitor as the primary monitor and the only one enabled due to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040
I haven't enabled the workaround described above: `Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then reboot.`

While not related to this crash: it would be great if the login screen appears on the primary device, which in my case is the external HDMI one. The login currently appears on the internal display.

[Zingam (registrirayme)]

I don't see if any logs were added from my crash and I couldn't figure out how to do that manually on time.

[Kjetil L (oddsignals)]

Consistently crashes on 22.10 when closing KeePass run under Mono.

Steps to reproduce:

1. Download and extract KeePass 2.51.1 Portable: https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.51.1/KeePass-2.51.1.zip/download
2. Install necessary packages:
  apt install mono-runtime
  apt install libmono-system-windows-forms4.0-cil
  apt install libcanberra-gtk-module
3. Run 'mono KeePass.exe'
4. After the application opens, exit it via File -> Exit or closing thw application window

[Yi (yippeeyo)]

Also getting this after updating to 22.04 over the weekend.

Ubuntu crash report dialog points identifies as 'DuplicateOf' 'https://bugs.launchpad.net/bugs/1959507.

running: journalctl -n 300 /usr/bin/gnome-shell

...indicates the following:
Sep 12 15:18:15 workstation2 gnome-shell[15595]: **
Sep 12 15:18:15 workstation2 gnome-shell[15595]: libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
Sep 12 15:18:15 workstation2 gnome-shell[15595]: Bail out! libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
Sep 12 15:18:15 workstation2 gnome-shell[15595]: GNOME Shell crashed with signal 6

...does it help?

[Daniel van Vugt (vanvugt)]

Unfortunately the bots are wrong in directing so many people to this bug.

Comment #13 is describing bug 1970917.

The problem with the bots is bug 1982283.

[Yi (yippeeyo)]

Apologies for #13. Added below in case anyone else ends up here for the same thing...

I had multiple monitors configured using ARandR, I'm working around the random crashes by disabling my second monitor via Settings>Screen Display>Single Display. Only one display, but better than crashing when one of the displays times out.

[Daniel van Vugt (vanvugt)]

In later releases this has become bug 2016214.

[Daniel van Vugt (vanvugt)]

The fix for this one was in 3.37.3 so that clearly wasn't enough:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1349

[Daniel van Vugt (vanvugt)]

Same for this fix in 41.0:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1935

Still not enough.

[Daniel van Vugt (vanvugt)]

That was a bot error. The duplicate bug is not related to this one.

[corrado venturini (corradoventu)]

I had this problem on my Ubuntu Noble. Attaching journalctl

[Daniel van Vugt (vanvugt)]

Unless your log mentions "clutter_actor_get_real_resource_scale" or "guessed_scale", I fear most people will land here by accident. The reason seems to be that our bots don't adequately distinguish between different assertion failures, which is bug 1982283.

The log in comment #20 doesn't even seem to be an assertion failure, but some unknown Xwayland crash/error:

Mar 01 09:49:15 corrado-n2-nn-0220 gnome-shell[1443]: Connection to xwayland lost
Mar 01 09:49:15 corrado-n2-nn-0220 gnome-shell[1443]: Xwayland terminated, exiting since it was mandatory

so please open a new bug for that if you can find the /var/crash file for it.

[sam tygier (samtygier)]

On noble I am getting a few gnome-shell crashes per day, and the bug reporter sends me here, which I guess is not right. In journalctl I get

Mar 10 16:31:44 t470s gnome-shell[20747]: Clutter:ERROR:../clutter/clutter/clutter-actor.c:5476:clutter_actor_dispose: assertion failed: (priv->parent == NULL)
Mar 10 16:31:44 t470s gnome-shell[20747]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-actor.c:5476:clutter_actor_dispose: assertion failed: (priv->parent == NULL)
Mar 10 16:31:44 t470s gnome-shell[20747]: GNOME Shell crashed with signal 6
Mar 10 16:31:44 t470s gnome-shell[20747]: == Stack trace for context 0x5d431b662140 ==
Mar 10 16:31:44 t470s gnome-shell[20747]: #0 5d431b729070 i resource:///org/gnome/shell/ui/popupMenu.js:802 (b95db5f2970 @ 104)
Mar 10 16:31:44 t470s gnome-shell[20747]: #1 5d431b728fe0 i resource:///org/gnome/shell/ui/popupMenu.js:815 (b95db5f2a10 @ 32)
Mar 10 16:31:44 t470s gnome-shell[20747]: #2 5d431b728f60 i resource:///org/gnome/shell/ui/popupMenu.js:1208 (b95db5f3470 @ 17)
Mar 10 16:31:44 t470s gnome-shell[20747]: #3 5d431b728ec0 i resource:///org/gnome/shell/ui/popupMenu.js:802 (b95db5f2970 @ 104)
Mar 10 16:31:44 t470s gnome-shell[20747]: #4 5d431b728dc8 i file:///<email address hidden>/appIcons.js:1043 (3c6652053380 @ 33)
Mar 10 16:31:44 t470s gnome-shell[20747]: #5 5d431b728d38 i file:///<email address hidden>/appIcons.js:1038 (3c6652053330 @ 17)
Mar 10 16:31:44 t470s gnome-shell[20747]: #6 5d431b728c88 i file:///<email address hidden>/appIcons.js:458 (3c6652052560 @ 346)
Mar 10 16:31:44 t470s gnome-shell[20747]: #7 5d431b728be8 i resource:///org/gnome/shell/ui/appDisplay.js:3100 (34a21fd931f0 @ 127)
Mar 10 16:31:44 t470s gnome-shell[20747]: #8 5d431b728b58 i resource:///org/gnome/shell/ui/init.js:21 (b95db570bf0 @ 48)

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6868 suggests this is an extension issue, and the trace mentions the ubuntu-dock extension.

[Marcos Alano (mhalano)]

Yeah, I opened a bug report for that: https://bugs.launchpad.net/bugs/2056506
It's the Ubuntu Dock extension the culprit. I downgraded it and the problem was gone.
Now we need to bisect to see what change caused this.