GNOME Shell

gnome-shell crashed in meta_workspace_index: Workspace does not exist to index!

Bug #1868293 reported by Joussef Jouda on 2020-03-20

This bug affects 3 people

	Status	Importance	Assigned to
GNOME Shell	New	Unknown	auto-gitlab.gnome.org-gnome-gnome-shell-- #4126
Mutter	New	Unknown	auto-gitlab.gnome.org-gnome-mutter #349
gnome-shell (Ubuntu)	Confirmed	Medium	Unassigned
mutter (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

https://errors.ubuntu.com/problem/5340b1db97f4c8202e6c7a695097f4f6c22a0695

---

gnome-shell crashed when I tried to move fireforx from one workspace to another.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 20 18:49:14 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-03-20 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
meta_bug () at /lib/x86_64-linux-gnu/libmutter-6.so.0
meta_workspace_index () at /lib/x86_64-linux-gnu/libmutter-6.so.0
() at /lib/x86_64-linux-gnu/libffi.so.7
() at /lib/x86_64-linux-gnu/libffi.so.7
() at /lib/libgjs.so.0
Title: gnome-shell crashed with SIGABRT in meta_bug()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

See original description

Tags:

Revision history for this message

Joussef Jouda (joussefnl) wrote on 2020-03-20:

Dependencies.txt Edit (21.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (922 bytes, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (1.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (131.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (290 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (186.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ShellJournal.txt Edit (43.6 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (26.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2020-03-20:

StacktraceTop:
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
__GI_abort () at abort.c:79
meta_bug (format=format@entry=0x7f98a2792660 "Workspace does not exist to index!\n") at ../src/core/util.c:423
meta_workspace_index (workspace=<optimized out>) at ../src/core/workspace.c:677
ffi_call_unix64 () at ../src/x86/unix64.S:101

Revision history for this message

Apport retracing service (apport) wrote on 2020-03-20: Stacktrace.txt

Stacktrace.txt Edit (3.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2020-03-20: StacktraceSource.txt

StacktraceSource.txt Edit (1.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2020-03-20: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (101.8 KiB, text/plain)

Changed in gnome-shell (Ubuntu):
importance:	Undecided → Medium
summary:	- gnome-shell crashed with SIGABRT in meta_bug() when I tried to move + gnome-shell crashed with SIGABRT in __GI_raise() when I tried to move fireforx from one workspace to another
tags:	removed: need-amd64-retrace

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-03-23:

Tracking in https://errors.ubuntu.com/problem/5340b1db97f4c8202e6c7a695097f4f6c22a0695

summary:	- gnome-shell crashed with SIGABRT in __GI_raise() when I tried to move - fireforx from one workspace to another + gnome-shell crashed in meta_workspace_index: Workspace does not exist to + index!
information type:	Private → Public
description:	updated

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-03-23:

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

Changed in gnome-shell (Ubuntu):
status:	New → Confirmed
Changed in mutter (Ubuntu):
status:	New → Confirmed

Daniel van Vugt (vanvugt) on 2020-03-23

Changed in mutter (Ubuntu):
importance:	Undecided → Medium
tags:	added: bionic eoan

Bug Watch Updater (bug-watch-updater) on 2020-03-30

Changed in gnome-shell:
status:	Unknown → New

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-04-02:

#10

Tracking in: https://gitlab.gnome.org/GNOME/mutter/issues/349

But maybe we should use: https://gitlab.gnome.org/GNOME/mutter/-/issues/1151

Daniel van Vugt (vanvugt) on 2020-08-07

tags:

removed: eoan

Revision history for this message

Marius Zaharie (zbmarius) wrote on 2020-10-02:

#11

I'm from an upgraded ubuntu 20.04 notebook that freezes less than 1 minute after login. The only time it unfrozen a bit it thrown the popup with this error. Well, at least there was the link to this bug as duplicate or something.

The solution they suggested here https://forums.developer.nvidia.com/t/ubuntu-20-04-screen-freezes-after-5-minutes-of-uptime-with-nvidia-drivers/122297 didn't work.
So I think it's something in gnome--ubuntu20.04