Ubuntu
gnome-shell package

gnome-shell crashes on display hotplug

Bug #1941983 reported by Brian Rogers on 2021-08-29

This bug report is a duplicate of: Bug #1871262: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed. Edit Remove

8

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	New	Undecided	Unassigned

Bug Description

$ lsb_release -rd
Description: Ubuntu Impish Indri (development branch)
Release: 21.10

gnome-shell 40.2-1ubuntu1

High likelihood of crashing (~75%) when plugging or unplugging an external monitor from my laptop, and it returns me to the login screen.

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 28 23:16:57 2021
DisplayManager: gdm3
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1625643042
InstallationDate: Installed on 2019-12-05 (633 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/brian
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:49
()
<signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
() at /lib/x86_64-linux-gnu/libmutter-8.so.0
() at /lib/x86_64-linux-gnu/libmutter-8.so.0
Title: gnome-shell crashed with SIGSEGV in __GI_raise()
UpgradeStatus: Upgraded to impish on 2021-08-05 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Tags:

Revision history for this message

Brian Rogers (brian-rogers) wrote on 2021-08-29:

#1

Dependencies.txt Edit (21.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (922 bytes, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (4.9 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (50.5 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (182.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1017 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (233 bytes, text/plain; charset="utf-8")
ShellJournal.txt Edit (10.8 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (37.4 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2021-08-29

tags:

removed: need-amd64-retrace

Revision history for this message

Brian Rogers (brian-rogers) wrote on 2021-08-31:

#2

I had trouble getting apport to upload this initially and had manually run apport-retrace on it by the time I got it to upload properly. I manually deleted the coredump and set this to public since the apport bot didn't do that on its own (it just removed the need-amd64-retrace tag).

If there's an issue I can get another crash report.

information type:

Private → Public

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-08-31:

#3

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 1871262, 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.

Revision history for this message

Brian Rogers (brian-rogers) wrote on 2021-10-14 (last edit on 2021-10-14):

#4

Are you sure about duplicate status? This is a new issue I'm experiencing with 21.10, and the reproduction steps are different (I see nothing in the other bug about display hotplug).

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-10-14:

#5

Your system log ends with:

[ 327.514699] ozmodiar gnome-shell[3502]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

So yes I think bug 1871262 is appropriate even if the steps are different. It gives the dozen or so affected people a central location to discuss their findings.

Also the rarity of the crash provides no evidence that the original cause was ever fixed. And indeed the issue is still open upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/930

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1871262 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

auto-gitlab.gnome.org-gnome-mutter-- #930
[opened] Edit

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