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

Bug #1959507 reported by Michel PIGUEL
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

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:

Revision history for this message
Michel PIGUEL (pigmy31) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGABRT in __pthread_kill_implementation()
+ gnome-shell crashed with assertion failed: (guessed_scale >= 1.f)
summary: - gnome-shell crashed with assertion failed: (guessed_scale >= 1.f)
+ gnome-shell crashed in clutter_actor_get_real_resource_scale() with
+ assertion failed: (guessed_scale >= 1.f)
information type: Private → Public
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Zingam (registrirayme) wrote :

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.

Revision history for this message
Zingam (registrirayme) wrote :

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.

tags: added: kinetic
Revision history for this message
Kjetil L (oddsignals) wrote :

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

Revision history for this message
Yi (yippeeyo) wrote :

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?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Revision history for this message
Yi (yippeeyo) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.